From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>
Cc: Avi Kivity <avi@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm-devel <kvm@vger.kernel.org>
Subject: Re: [PATCH] qemu-kvm: Fix segfault on -no-kvm startup
Date: Fri, 25 Sep 2009 21:03:11 +0200 [thread overview]
Message-ID: <4ABD13EF.7090403@web.de> (raw)
In-Reply-To: <20090925170548.GA30416@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1386 bytes --]
Gleb Natapov wrote:
> On Fri, Sep 25, 2009 at 06:05:49PM +0200, Jan Kiszka wrote:
>> The check for in-kernel irqchip must be protected by kvm_enabled, and we
>> have a different wrapper for it.
>>
> Why not move kvm_enabled() into kvm_irqchip_in_kernel()? It will return
> false if !kvm_enabled().
Yes, possible. But I'm not sure if it's worth to refactor at this level.
I think the whole irqchip interface has to go through some broader
refactoring when pushing it upstream. The result should either be a
specific, in-kernel-irqchip apic device or generic wrapper services that
cover all cases, is easily compiled away in the absence of KVM and avoid
#ifdefs like below.
Jan
>
>> Signed-off-by: Jan Kiszka <jan.kiszka@siemens.com>
>> ---
>>
>> hw/apic.c | 3 ++-
>> 1 files changed, 2 insertions(+), 1 deletions(-)
>>
>> diff --git a/hw/apic.c b/hw/apic.c
>> index 3a2e128..01ac174 100644
>> --- a/hw/apic.c
>> +++ b/hw/apic.c
>> @@ -509,9 +509,10 @@ void apic_init_reset(CPUState *env)
>>
>> env->halted = !(s->apicbase & MSR_IA32_APICBASE_BSP);
>> #ifdef KVM_CAP_MP_STATE
>> - if (kvm_irqchip_in_kernel(kvm_context))
>> + if (kvm_enabled() && qemu_kvm_irqchip_in_kernel()) {
>> env->mp_state
>> = env->halted ? KVM_MP_STATE_UNINITIALIZED : KVM_MP_STATE_RUNNABLE;
>> + }
>> #endif
>> }
>>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
next prev parent reply other threads:[~2009-09-25 19:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-25 16:05 [PATCH] qemu-kvm: Fix segfault on -no-kvm startup Jan Kiszka
2009-09-25 17:05 ` Gleb Natapov
2009-09-25 19:03 ` Jan Kiszka [this message]
2009-09-27 8:33 ` Avi Kivity
2009-09-27 8:33 ` 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=4ABD13EF.7090403@web.de \
--to=jan.kiszka@web.de \
--cc=avi@redhat.com \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.