LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Rohit Seth <rohitseth@google.com>
To: "'Hugh Dickins'" <hugh@veritas.com>
Cc: "'Nick Piggin'" <nickpiggin@yahoo.com.au>,
"'Mike Stroyan'" <mike.stroyan@hp.com>,
"'Andrew Morton'" <akpm@linux-foundation.org>,
"'Luck, Tony'" <tony.luck@intel.com>,
<linux-ia64@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: Fw: [PATCH] ia64: race flushing icache in do_no_page path
Date: Sat, 28 Apr 2007 11:17:45 -0700 [thread overview]
Message-ID: <200704281817.l3SIHu0P001764@smtp.corp.google.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0704280620150.9554@blonde.wat.veritas.com>
Hi Hugh,
-----Original Message-----
From: Hugh Dickins [mailto:hugh@veritas.com]
Sent: Friday, April 27, 2007 10:34 PM
To: Rohit Seth
Cc: Nick Piggin; Mike Stroyan; Andrew Morton; Luck, Tony;
linux-ia64@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: Fw: [PATCH] ia64: race flushing icache in do_no_page path
On Fri, 27 Apr 2007, Rohit Seth wrote:
> lazy_mmu_prot_update was added specifically for notifying change in
> protection. So, in a way it is closer to update_mmu_cache (Which is
> for change in mappings itself). Though for ia64 implementation, this
> ends up flushing the icaches when needed.
>The ia64 implementation is the only one which has any use for it,
Even Itanium didn't need it for almost 5 years :) Though I think archs that
have incoherent I & D caches could be (theoritically) exposed to same
(original) mprotect code path bug that triggered this API.
>and
>it's only interested when it's executable i.e. "lazy_mmu_prot_update"
>is a name concealing some overdesign.
You are right that ia64 is only interested in whne the execute permissions
kick in (and FWIW ia64 used to use update_mmu_cache API to do what it is now
doing lazy_mmu_prot_update). Though the idea was to design an API that any
arch can use to know when ever there is change in protections on a mapping.
Cheers,
-rohit
next prev parent reply other threads:[~2007-04-28 18:18 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070425205548.fd51b301.akpm@linux-foundation.org>
2007-04-26 7:53 ` Nick Piggin
2007-04-26 17:35 ` Mike Stroyan
2007-04-27 11:55 ` Nick Piggin
2007-04-27 14:18 ` Hugh Dickins
2007-04-27 17:02 ` David Mosberger-Tang
2007-04-28 1:31 ` Rohit Seth
2007-04-28 5:34 ` Hugh Dickins
2007-04-28 18:17 ` Rohit Seth [this message]
2007-05-01 11:52 ` Nick Piggin
2007-05-02 0:36 ` Rohit Seth
2007-05-02 2:05 ` Nick Piggin
2007-04-28 2:16 ` Nick Piggin
2007-04-28 1:24 ` Rohit Seth
2007-04-28 2:00 ` Nick Piggin
2007-04-28 3:04 ` Nick Piggin
2007-04-28 5:20 ` Hugh Dickins
2007-04-28 6:03 ` Nick Piggin
2007-04-28 18:30 ` Rohit Seth
2007-05-01 11:47 ` Nick Piggin
2007-05-02 0:36 ` Rohit Seth
2007-04-28 18:05 ` Rohit Seth
2007-05-01 11:43 ` Nick Piggin
2007-05-04 21:32 ` Mike Stroyan
2007-04-28 4:11 ` Nick Piggin
2007-04-28 17:57 ` Rohit Seth
2007-05-01 11:39 ` Nick Piggin
2007-05-02 0:36 ` Rohit Seth
2007-05-02 1:57 ` Nick Piggin
2007-07-04 14:24 Zoltan Menyhart
2007-07-04 16:58 ` KAMEZAWA Hiroyuki
2007-07-05 8:57 ` Zoltan Menyhart
2007-07-05 17:36 ` Mike Stroyan
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=200704281817.l3SIHu0P001764@smtp.corp.google.com \
--to=rohitseth@google.com \
--cc=akpm@linux-foundation.org \
--cc=hugh@veritas.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mike.stroyan@hp.com \
--cc=nickpiggin@yahoo.com.au \
--cc=tony.luck@intel.com \
--subject='RE: Fw: [PATCH] ia64: race flushing icache in do_no_page path' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).