[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20100304214030.GI13417@n2100.arm.linux.org.uk>
Date: Thu, 4 Mar 2010 21:40:30 +0000
From: Russell King - ARM Linux <linux@....linux.org.uk>
To: Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc: James Bottomley <James.Bottomley@...senPartnership.com>,
Pavel Machek <pavel@....cz>, mdharm-kernel@...-eyed-alien.net,
oliver@...kum.org, tom.leiming@...il.com, greg@...ah.com,
x0082077@...com, sshtylyov@...mvista.com,
Catalin Marinas <catalin.marinas@....com>,
bigeasy@...utronix.de, linux-usb@...r.kernel.org,
linux-kernel@...r.kernel.org,
FUJITA Tomonori <fujita.tomonori@....ntt.co.jp>,
santosh.shilimkar@...com, linux-arm-kernel@...ts.infradead.org
Subject: Re: USB mass storage and ARM cache coherency
On Fri, Mar 05, 2010 at 08:28:34AM +1100, Benjamin Herrenschmidt wrote:
> I don't think there's a core or driver problem in this specific case. As
> we discussed earlier, I believe the problem is that ARM considers a
> fresh page out of the page cache as "clean" instead of "dirty", and
> inverting that like we do on powerpc will fix their problem too.
The only concern is that it means we treat anonymous pages as dirty
by default.
That's quite sub-optimal since we take care (eg) on write faults to
copy the page and take care of the cache issues while we do that -
whether that be remapping the page to be coherent with the user
address, or cleaning each cache line as we copy the data.
Of course, the simple solution is to also arrange for PG_arch_1 to be
set in this case.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists