From: Jeremy Fitzhardinge <jeremy@goop.org>
To: paulmck@linux.vnet.ibm.com
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Avi Kivity <avi@redhat.com>,
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: Fri, 20 Mar 2009 08:38:46 -0700 [thread overview]
Message-ID: <49C3B886.8080408@goop.org> (raw)
In-Reply-To: <20090320044029.GD6807@linux.vnet.ibm.com>
Paul E. McKenney wrote:
>> Ah, interesting. So disabling interrupts prevents the RCU free from
>> happening, and non-atomic pte fetching is a non-issue. So it doesn't
>> address the PAE side of the problem.
>>
>
> This would be rcu_sched, correct?
>
I guess? Whatever it is that ends up calling all the rcu callbacks
after the idle. A cpu with disabled interrupts can't go through idle,
right? Or is there an explicit way to hold off rcu?
J
WARNING: multiple messages have this Message-ID (diff)
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: paulmck@linux.vnet.ibm.com
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
Avi Kivity <avi@redhat.com>,
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: Fri, 20 Mar 2009 08:38:46 -0700 [thread overview]
Message-ID: <49C3B886.8080408@goop.org> (raw)
In-Reply-To: <20090320044029.GD6807@linux.vnet.ibm.com>
Paul E. McKenney wrote:
>> Ah, interesting. So disabling interrupts prevents the RCU free from
>> happening, and non-atomic pte fetching is a non-issue. So it doesn't
>> address the PAE side of the problem.
>>
>
> This would be rcu_sched, correct?
>
I guess? Whatever it is that ends up calling all the rcu callbacks
after the idle. A cpu with disabled interrupts can't go through idle,
right? Or is there an explicit way to hold off rcu?
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-20 15:38 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:17 Question about x86/mm/gup.c's use of disabled interrupts Jeremy Fitzhardinge
2009-03-18 19:17 ` Jeremy Fitzhardinge
2009-03-18 19:17 ` Jeremy Fitzhardinge
2009-03-18 21:13 ` Avi Kivity
2009-03-18 21:13 ` Avi Kivity
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:23 ` Jeremy Fitzhardinge
2009-03-18 21:40 ` Avi Kivity
2009-03-18 21:40 ` Avi Kivity
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:14 ` Jeremy Fitzhardinge
2009-03-18 22:41 ` Avi Kivity
2009-03-18 22:41 ` Avi Kivity
2009-03-18 22:55 ` Jeremy Fitzhardinge
2009-03-18 22:55 ` Jeremy Fitzhardinge
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:05 ` Avi Kivity
2009-03-18 23:32 ` Jeremy Fitzhardinge
2009-03-18 23:32 ` Jeremy Fitzhardinge
2009-03-19 9:46 ` Avi Kivity
2009-03-19 9:46 ` Avi Kivity
2009-03-19 17:16 ` Jeremy Fitzhardinge
2009-03-19 17:16 ` Jeremy Fitzhardinge
2009-03-19 17:16 ` Jeremy Fitzhardinge
2009-03-19 17:33 ` Avi Kivity
2009-03-19 17:33 ` Avi Kivity
2009-04-03 2:41 ` paravirtops kernel and HVM guests Nitin A Kamble
2009-04-03 3:37 ` Jeremy Fitzhardinge
[not found] ` <70513aa50903181617r418ec23s744544dccfd812e8@mail.gmail.com>
2009-03-18 23:37 ` Question about x86/mm/gup.c's use of disabled interrupts Jeremy Fitzhardinge
2009-03-18 23:37 ` Jeremy Fitzhardinge
2009-03-19 1:32 ` Nick Piggin
2009-03-19 1:32 ` Nick Piggin
2009-03-19 17:31 ` Jeremy Fitzhardinge
2009-03-19 17:31 ` Jeremy Fitzhardinge
2009-03-20 4:40 ` Paul E. McKenney
2009-03-20 4:40 ` Paul E. McKenney
2009-03-20 15:38 ` Jeremy Fitzhardinge [this message]
2009-03-20 15:38 ` Jeremy Fitzhardinge
2009-03-20 15:57 ` Paul E. McKenney
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=49C3B886.8080408@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=paulmck@linux.vnet.ibm.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 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.