* Re: [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest
[not found] ` <1341576018-10721-3-git-send-email-fweisbec@gmail.com>
@ 2012-07-08 15:54 ` Avi Kivity
2012-07-09 17:45 ` Frederic Weisbecker
0 siblings, 1 reply; 2+ messages in thread
From: Avi Kivity @ 2012-07-08 15:54 UTC (permalink / raw)
To: Frederic Weisbecker
Cc: Paul E. McKenney, LKML, Alessio Igor Bogani, Andrew Morton,
Chris Metcalf, Christoph Lameter, Geoff Levand, Gilad Ben Yossef,
Hakan Akkan, H. Peter Anvin, Ingo Molnar, Josh Triplett,
Kevin Hilman, Max Krasnyansky, Peter Zijlstra, Stephen Hemminger,
Steven Rostedt, Sven-Thorsten Dietrich, Thomas Gleixner,
Marcelo Tosatti, KVM list
On 07/06/2012 03:00 PM, Frederic Weisbecker wrote:
> Allow calls to rcu_user_enter() even if we are already
> in userspace (as seen by RCU) and allow calls to rcu_user_exit()
> even if we are already in the kernel.
>
> This makes the APIs more flexible to be called from architectures.
> Exception entries for example won't need to know if they come from
> userspace before calling rcu_user_exit().
I guess I should switch kvm to rcu_user_enter() and co, so we can
disable the tick while running in a guest. But where are those
functions? What are the rules for calling them?
--
error compiling committee.c: too many arguments to function
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest
2012-07-08 15:54 ` [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest Avi Kivity
@ 2012-07-09 17:45 ` Frederic Weisbecker
0 siblings, 0 replies; 2+ messages in thread
From: Frederic Weisbecker @ 2012-07-09 17:45 UTC (permalink / raw)
To: Avi Kivity
Cc: Paul E. McKenney, LKML, Alessio Igor Bogani, Andrew Morton,
Chris Metcalf, Christoph Lameter, Geoff Levand, Gilad Ben Yossef,
Hakan Akkan, H. Peter Anvin, Ingo Molnar, Josh Triplett,
Kevin Hilman, Max Krasnyansky, Peter Zijlstra, Stephen Hemminger,
Steven Rostedt, Sven-Thorsten Dietrich, Thomas Gleixner,
Marcelo Tosatti, KVM list
On Sun, Jul 08, 2012 at 06:54:18PM +0300, Avi Kivity wrote:
> On 07/06/2012 03:00 PM, Frederic Weisbecker wrote:
> > Allow calls to rcu_user_enter() even if we are already
> > in userspace (as seen by RCU) and allow calls to rcu_user_exit()
> > even if we are already in the kernel.
> >
> > This makes the APIs more flexible to be called from architectures.
> > Exception entries for example won't need to know if they come from
> > userspace before calling rcu_user_exit().
>
> I guess I should switch kvm to rcu_user_enter() and co, so we can
> disable the tick while running in a guest. But where are those
> functions? What are the rules for calling them?
I guess we need to have a closer look at the guest case first. We probably need
to take some care about specifics in time and load accounting usually
handled by the tick before we can shut it down. RCU is only part of the
problem.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2012-07-09 17:45 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <1341576018-10721-1-git-send-email-fweisbec@gmail.com>
[not found] ` <1341576018-10721-3-git-send-email-fweisbec@gmail.com>
2012-07-08 15:54 ` [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest Avi Kivity
2012-07-09 17:45 ` Frederic Weisbecker
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox