public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Avi Kivity <avi@redhat.com>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
	Zachary Amsden <zamsden@redhat.com>
Subject: Re: [PATCH 2/2] KVM: Convert read-only users of vm_list to RCU
Date: Thu, 10 Feb 2011 12:31:55 +0100	[thread overview]
Message-ID: <4D53CCAB.8040204@siemens.com> (raw)
In-Reply-To: <4D53BB02.20206@redhat.com>

On 2011-02-10 11:16, Avi Kivity wrote:
> On 02/08/2011 01:55 PM, Jan Kiszka wrote:
>> Only for walking the list of VMs, we do not need to hold the preemption
>> disabling kvm_lock. Convert stat services, the cpufreq callback and
>> mmu_shrink to RCU. For the latter, special care is required to
>> synchronize its list_move_tail with kvm_destroy_vm.
>>
>>
>> diff --git a/arch/x86/kvm/mmu.c b/arch/x86/kvm/mmu.c
>> index b6a9963..e9d0ed8 100644
>> --- a/arch/x86/kvm/mmu.c
>> +++ b/arch/x86/kvm/mmu.c
>> @@ -3587,9 +3587,9 @@ static int mmu_shrink(struct shrinker *shrink, int nr_to_scan, gfp_t gfp_mask)
>>   	if (nr_to_scan == 0)
>>   		goto out;
>>
>> -	raw_spin_lock(&kvm_lock);
>> +	rcu_read_lock();
>>
>> -	list_for_each_entry(kvm,&vm_list, vm_list) {
>> +	list_for_each_entry_rcu(kvm,&vm_list, vm_list) {
>>   		int idx, freed_pages;
>>   		LIST_HEAD(invalid_list);
> 
> Have to #include rculist.h,

OK.

> and to change all list operations on vm_list 
> to rcu variants.

Not sure if we have such variants for all cases...

> 
>>
>> @@ -3607,10 +3607,14 @@ static int mmu_shrink(struct shrinker *shrink, int nr_to_scan, gfp_t gfp_mask)
>>   		spin_unlock(&kvm->mmu_lock);
>>   		srcu_read_unlock(&kvm->srcu, idx);
>>   	}
>> -	if (kvm_freed)
>> -		list_move_tail(&kvm_freed->vm_list,&vm_list);
>> +	if (kvm_freed) {
>> +		raw_spin_lock(&kvm_lock);
>> +		if (!kvm->deleted)
>> +			list_move_tail(&kvm_freed->vm_list,&vm_list);
> 
> There is no list_move_tail_rcu().

...specifically not for this one.

> 
> Why check kvm->deleted?  it's in the process of being torn down anyway, 
> it doesn't matter if mmu_shrink or kvm_destroy_vm pulls the trigger.

kvm_destroy_vm removes a vm from the list while mmu_shrink is running.
Then mmu_shrink's list_move_tail will re-add that vm to the list tail
again (unless already the removal in move_tail produces a crash).

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-02-10 11:32 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4D512EF7.8040409@siemens.com>
2011-02-08 11:55 ` [PATCH 2/2] KVM: Convert read-only users of vm_list to RCU Jan Kiszka
2011-02-10 10:16   ` Avi Kivity
2011-02-10 11:31     ` Jan Kiszka [this message]
2011-02-10 12:34       ` Avi Kivity
2011-02-10 12:45         ` Jan Kiszka
2011-02-10 12:56           ` Avi Kivity
2011-02-10 12:57             ` Avi Kivity
2011-02-10 13:14               ` Jan Kiszka
2011-02-10 13:19                 ` Avi Kivity
2011-02-10 13:47                   ` Jan Kiszka
2011-02-10 14:26                     ` Avi Kivity
2011-02-10 14:34                       ` Jan Kiszka
2011-02-10 14:47                         ` Avi Kivity
2011-02-10 14:55                           ` Jan Kiszka
2011-02-15 12:32   ` Marcelo Tosatti
2011-02-15 14:08     ` Jan Kiszka

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=4D53CCAB.8040204@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=zamsden@redhat.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