From: benh@kernel.crashing.org (Benjamin Herrenschmidt)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH] ARM: Assume new page cache pages have dirty D-cache
Date: Fri, 05 Mar 2010 15:46:19 +1100 [thread overview]
Message-ID: <1267764379.22204.103.camel@pasglop> (raw)
In-Reply-To: <20100305012823.GD26618@linux-sh.org>
On Fri, 2010-03-05 at 10:28 +0900, Paul Mundt wrote:
> In the anonymous page case, flush_anon_page() is always called prior to
> flush_dcache_page(), so flush_anon_page() could just set PG_dcache_clean
> to work around that. That would handle get_user_pages(), too.
Well, currently, we clear PG_arch_1 in flush_dcache_page(), at least on
ppc.
Now, I have a nagging feeling that we might not need to... I'll have to
give it a closer look when I'm back from this extended week-end :-)
Cheers,
Ben.
WARNING: multiple messages have this Message-ID (diff)
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Paul Mundt <lethal@linux-sh.org>
Cc: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Catalin Marinas <catalin.marinas@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
James Bottomley <James.Bottomley@HansenPartnership.com>
Subject: Re: [RFC PATCH] ARM: Assume new page cache pages have dirty D-cache
Date: Fri, 05 Mar 2010 15:46:19 +1100 [thread overview]
Message-ID: <1267764379.22204.103.camel@pasglop> (raw)
In-Reply-To: <20100305012823.GD26618@linux-sh.org>
On Fri, 2010-03-05 at 10:28 +0900, Paul Mundt wrote:
> In the anonymous page case, flush_anon_page() is always called prior to
> flush_dcache_page(), so flush_anon_page() could just set PG_dcache_clean
> to work around that. That would handle get_user_pages(), too.
Well, currently, we clear PG_arch_1 in flush_dcache_page(), at least on
ppc.
Now, I have a nagging feeling that we might not need to... I'll have to
give it a closer look when I'm back from this extended week-end :-)
Cheers,
Ben.
next prev parent reply other threads:[~2010-03-05 4:46 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-02 17:34 [RFC PATCH] ARM: Assume new page cache pages have dirty D-cache Catalin Marinas
2010-03-02 17:34 ` Catalin Marinas
2010-03-04 16:44 ` Russell King - ARM Linux
2010-03-04 16:44 ` Russell King - ARM Linux
2010-03-04 17:27 ` Catalin Marinas
2010-03-04 17:27 ` Catalin Marinas
2010-03-04 18:36 ` Catalin Marinas
2010-03-04 18:36 ` Catalin Marinas
2010-03-04 21:44 ` Russell King - ARM Linux
2010-03-04 21:44 ` Russell King - ARM Linux
2010-03-05 1:28 ` Paul Mundt
2010-03-05 1:28 ` Paul Mundt
2010-03-05 4:46 ` Benjamin Herrenschmidt [this message]
2010-03-05 4:46 ` Benjamin Herrenschmidt
2010-03-05 4:32 ` Benjamin Herrenschmidt
2010-03-05 4:32 ` Benjamin Herrenschmidt
2010-03-05 16:52 ` Catalin Marinas
2010-03-05 16:52 ` Catalin Marinas
2010-03-05 21:16 ` Russell King - ARM Linux
2010-03-05 21:16 ` Russell King - ARM Linux
2010-03-06 10:00 ` Catalin Marinas
2010-03-06 10:00 ` Catalin Marinas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1267764379.22204.103.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.