[lkml]   [2000]   [Jul]   [22]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
Can anyone point out the logic of continued existance of flush_icache_range
after the introduction of flush_icache_page()? I admit that
flush_icache_range is still needed in the module loading code, but do we
need it anymore in the a.out loading code? That code should be incurring
page faults, which will do the flush_icache_page anyway. Seems like
double work to me to do flush_icache_range again after the loading has
been done.

This argument to delete the flush_icache_range calls from the a.out
loading code assumes that the f_op->read() code behaves sanely, ie does
not do unexpected things like touch the user address (thus allocating
the page, and doing the icache flush via the page fault handler much
earlier) before it starts reading the a.out sections in ...


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:57    [W:0.050 / U:4.880 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site