"David S. Miller" <[EMAIL PROTECTED]> wrote:
> From: Russell King <[EMAIL PROTECTED]>
> Date: Fri, 29 Jul 2005 16:13:43 +0100
>
>> My current patch to get this working is below.  The only thing which
>> really seems to fix the issue is the __flush_dcache_page call in
>> read_pages() - if I remove this, I get spurious segfaults and illegal
>> instruction faults.
>
> If one cpu stores, does it get picked up in the other cpu's I-cache?

It only gets picked up by the other CPU's D-cache (which is fully
coherent between cores). The I-cache needs to be invalidated on each
CPU.

> If not, you cannot use the lazy dcache flushing method, and in fact
> you must broadcast the flush on all processors.

Why wouldn't the lazy dcache flushing method work? My understanding is
that if there is no user mapping for a given page, there's no reason
to flush the dcache and just postpone it until the page is faulted
in. When the page fault occurs the dcache should be flushed (on one
CPU is enough) and the icache invalidated on all the CPUs.

-- 
Catalin

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Reply via email to