lkml.org 
[lkml]   [2011]   [Dec]   [28]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: [PATCH v6] kvm: make vcpu life cycle separated from kvm instance
On 12/28/2011 08:54 AM, Liu ping fan wrote:
> >>
> >> struct kvm_vcpu {
> >> struct kvm *kvm;
> >> + struct list_head list;
> >> #ifdef CONFIG_PREEMPT_NOTIFIERS
> >> struct preempt_notifier preempt_notifier;
> >> #endif
> >> @@ -251,12 +252,14 @@ struct kvm {
> >> struct mm_struct *mm; /* userspace tied to this vm */
> >> struct kvm_memslots *memslots;
> >> struct srcu_struct srcu;
> >> + struct srcu_struct srcu_vcpus;
> >> +
> >
> > Another srcu. This alone is worth explaining in the changelog IMO.
> >
> Sorry, but why? I think it is just a srcu, and because it has
> different aim and want a independent grace period, so not multiplex
> kvm->srcu.

There is Documentation/virtual/kvm/locking.txt for that.

btw, why does it have to be srcu? Is rcu insufficient?

Why do we want an independent grace period, is hotunplugging a vcpu that
much different from hotunplugging memory?

--
error compiling committee.c: too many arguments to function



\
 
 \ /
  Last update: 2011-12-28 10:55    [W:0.150 / U:0.084 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site