From: Andi Kleen <ak@suse.de>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: linux-arch@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Which architectures need to sync vmalloc mappings between processes?
Date: Sun, 18 Feb 2007 18:08:13 +0100 [thread overview]
Message-ID: <200702181808.13576.ak@suse.de> (raw)
In-Reply-To: <45D7E438.4020902@goop.org>
> On i386 with PAE, this is not necessary because the kernel's mappings
> are shared between all processes anyway, so it would be a no-op.
> However, non-PAE i386 has a separate kernel mapping for each process,
> and so needs to sync them - typically lazily on faults, but
> vmalloc_sync_all exists to allow mass syncing when required.
The only case that needs it right now on x86 is NMI handlers in modules
to avoid early IRETs that could cause NMI recursion.
That's a very obscure architecture specific quirk and I wouldn't expect any
other architecture to suffer from this.
-Andi
prev parent reply other threads:[~2007-02-18 17:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-18 5:29 Which architectures need to sync vmalloc mappings between processes? Jeremy Fitzhardinge
2007-02-18 14:55 ` James Bottomley
2007-02-18 17:08 ` Andi Kleen [this message]
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=200702181808.13576.ak@suse.de \
--to=ak@suse.de \
--cc=jeremy@goop.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox