public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Dong, Eddie" <eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: kvm-devel <kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: guest reboot error
Date: Sun, 30 Sep 2007 12:51:18 +0200	[thread overview]
Message-ID: <46FF7FA6.2000707@qumranet.com> (raw)
In-Reply-To: <10EA09EFD8728347A513008B6B0DA77A022AEB9A-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>

Dong, Eddie wrote:
> Avi Kivity wrote:
>   
>>> 	It is good that I don't need to push the kernel device reset
>>>       
> patch
>   
>>> out that soon, but we still need to do so for a graceful reset
>>> especially kernel devices need to be reseted since
>>>
>>>       
>> Yes, that patch is needed.  I thought of another way to do it: have a
>>     
>
> >From HW point of view, reset is just a signal of RST pin dessert.
> So here we can use a single API indicating dessert of RST pin (i.e.
> RESET)
>
>   
>> single vm ioctl reset, which can set a reset bit in all vcpu->requests
>> and then kick the vcpus.  When the vcpus execute, they'll
>> check the bit
>> and reset the cpu and lapic then; no locking needed.
>>
>>     
>
> The tricky thing is that when kernel is involved in reset, all VPs are
> already
> reseted and no longer execute. Setting the request bit doesn;t help.
>
>   

We wake them up in addition to setting the bit.  They'll reset when they 
see it.

> So far SMP guest reboot doesn't work no matter w/ or w/o kvm-irqchip. 
> I am wondering how we handle SMP reboot in Qemu since we extended
> Qemu SMP from single thread to multiple threads. This change will bring
> big impact to reboot since previously all reset, such as APIC reset,
> happens 
> in a single (own) thread, but now the apic reset may not happen in its 
> own thread.
>   

With -no-kvm-irqchip, the thread that takes the reset takes the big qemu 
lock and resets all vcpus and all lapics.  Last I tested it worked but 
maybe there has been a regression.

> By the way, extending from single thread to multiple thread SMP is a 
> big change to Qemu, is there any progress in Qemu community?
>   

The big issue is emulating read-modify-write instructions.  Once that's 
done there's the question of whether running qemu on smp will actually 
scale.


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


-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/

  parent reply	other threads:[~2007-09-30 10:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-27  9:58 guest reboot error Dong, Eddie
     [not found] ` <10EA09EFD8728347A513008B6B0DA77A022AE441-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-27 10:09   ` Dong, Eddie
     [not found]     ` <10EA09EFD8728347A513008B6B0DA77A022AE445-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-27 10:48       ` Avi Kivity
     [not found]         ` <46FB8A65.6000504-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-28  2:27           ` Dong, Eddie
     [not found]             ` <10EA09EFD8728347A513008B6B0DA77A022AE67A-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-28  8:56               ` Dong, Eddie
     [not found]                 ` <10EA09EFD8728347A513008B6B0DA77A022AE9B4-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-28 14:38                   ` Avi Kivity
     [not found]                     ` <46FD11C8.8040701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-29 10:29                       ` Dong, Eddie
     [not found]                         ` <10EA09EFD8728347A513008B6B0DA77A022AEB9A-wq7ZOvIWXbNpB2pF5aRoyrfspsVTdybXVpNB7YpNyf8@public.gmane.org>
2007-09-30 10:51                           ` Avi Kivity [this message]
2007-09-28 14:44               ` Avi Kivity

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=46FF7FA6.2000707@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=eddie.dong-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /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