From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Shentino <shentino@gmail.com>
Cc: Avi Kivity <avi@redhat.com>,
Nick Piggin <nickpiggin@yahoo.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Memory Management List <linux-mm@kvack.org>,
Xen-devel <xen-devel@lists.xensource.com>,
Jan Beulich <jbeulich@novell.com>, Ingo Molnar <mingo@elte.hu>
Subject: Re: Question about x86/mm/gup.c's use of disabled interrupts
Date: Wed, 18 Mar 2009 16:37:24 -0700 [thread overview]
Message-ID: <49C185B4.90004@goop.org> (raw)
In-Reply-To: <70513aa50903181617r418ec23s744544dccfd812e8@mail.gmail.com>
Shentino wrote:
> But, does a CPU running a task in userspace effectively have a read
> lock on the page tables?
No. A process has its own user pagetable which the kernel maintains on
its behalf. The kernel will briefly take locks on it while doing
modifications, mostly to deal with multithreaded usermode code running
on multiple cpus.
J
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2009-03-18 23:37 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:17 Jeremy Fitzhardinge
2009-03-18 21:13 ` Avi Kivity
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:40 ` Avi Kivity
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:41 ` Avi Kivity
2009-03-18 22:55 ` Jeremy Fitzhardinge
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:32 ` Jeremy Fitzhardinge
2009-03-19 9:46 ` Avi Kivity
2009-03-19 17:16 ` Jeremy Fitzhardinge
2009-03-19 17:33 ` Avi Kivity
[not found] ` <70513aa50903181617r418ec23s744544dccfd812e8@mail.gmail.com>
2009-03-18 23:37 ` Jeremy Fitzhardinge [this message]
2009-03-19 1:32 ` Nick Piggin
2009-03-19 17:31 ` Jeremy Fitzhardinge
2009-03-20 4:40 ` Paul E. McKenney
2009-03-20 15:38 ` Jeremy Fitzhardinge
2009-03-20 15:57 ` Paul E. McKenney
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=49C185B4.90004@goop.org \
--to=jeremy@goop.org \
--cc=avi@redhat.com \
--cc=jbeulich@novell.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=shentino@gmail.com \
--cc=xen-devel@lists.xensource.com \
/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