From: Sahid Orentino Ferdjaoui <sferdjao@redhat.com>
To: "Xu, Anthony" <anthony.xu@intel.com>
Cc: "'qemu-devel@nongnu.org'" <qemu-devel@nongnu.org>,
'Paolo Bonzini' <pbonzini@redhat.com>,
'Stefan Hajnoczi' <stefanha@gmail.com>
Subject: Re: [Qemu-devel] [PATCH]Enable kvmvapic only when host doesn't support VAPIC capability in KVM mode
Date: Thu, 6 Apr 2017 13:58:54 +0200 [thread overview]
Message-ID: <20170406115854.GA29142@redhat> (raw)
In-Reply-To: <4712D8F4B26E034E80552F30A67BE0B1A4E842@ORSMSX112.amr.corp.intel.com>
On Wed, Apr 05, 2017 at 12:52:25AM +0000, Xu, Anthony wrote:
> In KVM mode, enable kvmvapic only when host doesn't support
> VAPIC capability.
>
> Save the time to set up kvmvapic in some hosts.
>
>
> Signed-off -by: Anthony Xu <anthony.xu@intel.com>
>
s/Signed-off -by/Signed-off-by
nit: I think we do prefer a single line summary for the commit
message, a detailed description of the patch and only one blank line
to separe the Signed-off-by tag [0].
>
> diff --git a/hw/intc/apic_common.c b/hw/intc/apic_common.c
> index c3829e3..d5c53af 100644
> --- a/hw/intc/apic_common.c
> +++ b/hw/intc/apic_common.c
> @@ -317,8 +317,11 @@ static void apic_common_realize(DeviceState *dev, Error **errp)
> info = APIC_COMMON_GET_CLASS(s);
> info->realize(dev, errp);
>
> - /* Note: We need at least 1M to map the VAPIC option ROM */
> + /* Note: We need at least 1M to map the VAPIC option ROM,
> + if it is KVM, enable kvmvapic only when KVM doesn't have
> + VAPIC capability */
> if (!vapic && s->vapic_control & VAPIC_ENABLE_MASK &&
> + (!kvm_enabled() || (kvm_enabled() && !kvm_has_vapic())) &&
> !hax_enabled() && ram_size >= 1024 * 1024) {
> vapic = sysbus_create_simple("kvmvapic", -1, NULL);
> }
> diff --git a/include/sysemu/kvm.h b/include/sysemu/kvm.h
> index 24281fc..43e0e4c 100644
> --- a/include/sysemu/kvm.h
> +++ b/include/sysemu/kvm.h
> @@ -215,6 +215,7 @@ extern KVMState *kvm_state;
>
> bool kvm_has_free_slot(MachineState *ms);
> int kvm_has_sync_mmu(void);
> +int kvm_has_vapic(void);
> int kvm_has_vcpu_events(void);
> int kvm_has_robust_singlestep(void);
> int kvm_has_debugregs(void);
> diff --git a/kvm-all.c b/kvm-all.c
> index 90b8573..edcb6ea 100644
> --- a/kvm-all.c
> +++ b/kvm-all.c
> @@ -2232,6 +2232,10 @@ int kvm_has_sync_mmu(void)
> return kvm_check_extension(kvm_state, KVM_CAP_SYNC_MMU);
> }
>
> +int kvm_has_vapic(void){
> + return !kvm_check_extension(kvm_state, KVM_CAP_VAPIC);
> +}
> +
Is that function shouldn't return true if KVM is providing VAPIC
capability?
nit: I think you need to mark a return to the line before opening
brace for a function [1].
[0] http://wiki.qemu-project.org/Contribute/SubmitAPatch#Write_a_meaningful_commit_message
[1] http://git.qemu-project.org/?p=qemu.git;a=blob_plain;f=CODING_STYLE;hb=HEAD
> int kvm_has_vcpu_events(void)
> {
> return kvm_state->vcpu_events;
next prev parent reply other threads:[~2017-04-06 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-05 0:52 [Qemu-devel] [PATCH]Enable kvmvapic only when host doesn't support VAPIC capability in KVM mode Xu, Anthony
2017-04-06 11:58 ` Sahid Orentino Ferdjaoui [this message]
2017-04-06 18:18 ` Xu, Anthony
2017-04-10 12:53 ` Sahid Orentino Ferdjaoui
2017-04-11 0:54 ` Xu, Anthony
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=20170406115854.GA29142@redhat \
--to=sferdjao@redhat.com \
--cc=anthony.xu@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=stefanha@gmail.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.