From: Jan Kiszka <jan.kiszka@web.de>
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: Tue, 02 Jun 2009 22:35:47 +0200 [thread overview]
Message-ID: <4A258D23.9080106@web.de> (raw)
In-Reply-To: <1243971470-31676-2-git-send-email-glommer@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 968 bytes --]
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?
>
> Signed-off-by: Glauber Costa <glommer@redhat.com>
> ---
> hw/apic.c | 3 +--
> 1 files changed, 1 insertions(+), 2 deletions(-)
>
> diff --git a/hw/apic.c b/hw/apic.c
> index 86aa6b6..2eddba0 100644
> --- a/hw/apic.c
> +++ b/hw/apic.c
> @@ -467,8 +467,7 @@ static void apic_init_ipi(APICState *s)
>
> cpu_reset(s->cpu_env);
>
> - if (!(s->apicbase & MSR_IA32_APICBASE_BSP) &&
> - (!kvm_enabled() || !qemu_kvm_irqchip_in_kernel()))
> + if (!(s->apicbase & MSR_IA32_APICBASE_BSP))
> s->cpu_env->halted = 1;
>
> if (kvm_enabled() && !qemu_kvm_irqchip_in_kernel())
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-06-02 20:35 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 ` Jan Kiszka [this message]
2009-06-02 21:23 ` [PATCH 1/4] always halt non-bsp cpu 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
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=4A258D23.9080106@web.de \
--to=jan.kiszka@web.de \
--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