From: Jan Kiszka <jan.kiszka@siemens.com>
To: Glauber Costa <glommer@redhat.com>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH 1/4] always halt non-bsp cpu.
Date: Wed, 03 Jun 2009 13:03:30 +0200 [thread overview]
Message-ID: <4A265882.6040704@siemens.com> (raw)
In-Reply-To: <20090603010159.GA30777@poweredge.glommer>
Glauber Costa wrote:
> On Wed, Jun 03, 2009 at 12:32:04AM +0200, Jan Kiszka wrote:
>> Glauber Costa wrote:
>>> On Wed, Jun 03, 2009 at 12:01:00AM +0200, Jan Kiszka wrote:
>>>> Glauber Costa wrote:
>>>>> On Tue, Jun 02, 2009 at 10:35:47PM +0200, Jan Kiszka wrote:
>>>>>> Glauber Costa wrote:
>>>>>>> This is not kvm specific, and should do fine in plain qemu
>>>>>> This is fine with plain qemu already. The problem, IIUC, is that
>>>>>> in-kernel kvm irqchip does not have a chance to remove the halted state
>>>>>> again. Did you test the effect of this patch on that scenario? What
>>>>>> makes it safe to be removed now?
>>>>> IIRC, the in kernel irqchip sets halted = 0 in the very beginning of
>>>>> the vcpu initialization.
>>>>>
>>>>> It is tested here with in-kernel irqchip and works, so probably not
>>>>> a problem, unless you can spot something.
>>>> At least your patch applied alone breaks -smp >1 here.
>>>>
>>>> But the whole management of env->halted for the in-kernel irqchip in
>>>> qemu-kvm is a bit hacky IMHO. Maybe it's time to rethink this. Would be
>>>> nice to always see a consistent halted in user space, specifically for
>>>> debugging purposes.
>>> out of curiosity: did you apply the whole series?
>> Meanwhile I did, but it makes no difference.
> Jan, can you be more specific on why it breaks? I'm double trying it
> here, and it works for me just fine.
>
It locked up in the BIOS after reset from a booted SMP guest, somewhere
before selecting the boot device.
Jan
--
Siemens AG, Corporate Technology, CT SE 2
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2009-06-03 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 19:37 [PATCH 0/4] Provide kvm-free implementations of apic/ioapic Glauber Costa
2009-06-02 19:37 ` [PATCH 1/4] always halt non-bsp cpu Glauber Costa
2009-06-02 19:37 ` [PATCH 2/4] sipi and init: move common code Glauber Costa
2009-06-02 19:37 ` [PATCH 3/4] provide a kvm-free implementation of apic Glauber Costa
2009-06-02 19:37 ` [PATCH 4/4] provide a kvm-free implementation of ioapic Glauber Costa
2009-06-02 20:35 ` [PATCH 1/4] always halt non-bsp cpu Jan Kiszka
2009-06-02 21:23 ` Glauber Costa
2009-06-02 22:01 ` Jan Kiszka
2009-06-02 22:09 ` Glauber Costa
2009-06-02 22:32 ` Jan Kiszka
2009-06-02 22:40 ` Glauber Costa
2009-06-03 1:01 ` Glauber Costa
2009-06-03 11:03 ` Jan Kiszka [this message]
2009-06-03 1:23 ` Glauber Costa
2009-06-03 11:01 ` Jan Kiszka
2009-06-03 11:11 ` Gleb Natapov
2009-06-03 10:32 ` Gleb Natapov
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=4A265882.6040704@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=avi@redhat.com \
--cc=glommer@redhat.com \
--cc=kvm@vger.kernel.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