public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Takuya Yoshikawa <yoshikawa.takuya@oss.ntt.co.jp>
To: Zachary Amsden <zamsden@redhat.com>
Cc: avi@redhat.com, mtosatti@redhat.com, kvm@vger.kernel.org,
	takuya.yoshikawa@gmail.com
Subject: Re: [PATCH 1/2] KVM: take kvm_lock for hardware_disable() during cpu hotplug
Date: Thu, 18 Nov 2010 17:33:41 +0900	[thread overview]
Message-ID: <4CE4E4E5.206@oss.ntt.co.jp> (raw)
In-Reply-To: <4CE4BD7E.3040406@redhat.com>

(2010/11/18 14:45), Zachary Amsden wrote:

>>> No, I believe your patch is correct and the lock should be there. Did you test with spinlock debugging just to be sure?
>>>
>>
>> Sorry but no.
>>
>> I have no experience with cpu hotplug.
>>
>> So I thought it would take too much time to do real test by myself and reported like this this time.
>>
>> Any easy way to test?
>
> Yes, quite easy. Some systems may not let cpu0 go offline, but you can manually disable and re-enable the other processors:
>
> [root@mysore ~]# echo "0" > /sys/devices/system/cpu/cpu1/online
> [root@mysore ~]# echo "1" > /sys/devices/system/cpu/cpu1/online
>
> Cheers,
>
> Zach


Thanks a lot!

I tried and got a log like this:

kernel: [  422.084620] kvm: disabling virtualization on CPU1
kernel: [  422.085757] CPU 1 is now offline
kernel: [  422.085766] lockdep: fixing up alternatives.
kernel: [  422.085780] SMP alternatives: switching to UP code
kernel: [  472.081069] lockdep: fixing up alternatives.
kernel: [  472.081080] SMP alternatives: switching to SMP code
kernel: [  472.099182] Booting Node 0 Processor 1 APIC 0x1
kernel: [  422.104799] kvm: enabling virtualization on CPU1

Working correctly, I think.


   Takuya

  reply	other threads:[~2010-11-18  8:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-16  8:32 [PATCH 0/2] KVM: fix and cleanup: kvm_lock and hardware_disable Takuya Yoshikawa
2010-11-16  8:35 ` [PATCH 1/2] KVM: take kvm_lock for hardware_disable() during cpu hotplug Takuya Yoshikawa
2010-11-18  1:59   ` Zachary Amsden
2010-11-18  2:04     ` Takuya Yoshikawa
2010-11-18  2:33       ` Zachary Amsden
2010-11-18  2:41         ` Takuya Yoshikawa
2010-11-18  5:45           ` Zachary Amsden
2010-11-18  8:33             ` Takuya Yoshikawa [this message]
2010-11-16  8:37 ` [PATCH 2/2] KVM: rename hardware_[dis|en]able() to *_nolock() and add locking wrappers Takuya Yoshikawa
2010-11-18 15:26 ` [PATCH 0/2] KVM: fix and cleanup: kvm_lock and hardware_disable Marcelo Tosatti

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=4CE4E4E5.206@oss.ntt.co.jp \
    --to=yoshikawa.takuya@oss.ntt.co.jp \
    --cc=avi@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mtosatti@redhat.com \
    --cc=takuya.yoshikawa@gmail.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