Re: [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest

[Frederic Weisbecker]

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.
--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: [PATCH 2/6] rcu: Allow rcu_user_enter()/exit() to nest

[Avi Kivity]

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


--
To unsubscribe from this list: send the line unsubscribe kvm in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html