All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Radim Krčmář" <rkrcmar@redhat.com>
To: zhanghailiang <zhang.zhanghailiang@huawei.com>
Cc: kvm@vger.kernel.org, gleb@kernel.org, pbonzini@redhat.com,
	peter.huangpeng@huawei.com
Subject: Re: [PATCH] KVM: add KVM_CAP_VMX_APICV to advertise hardware apic-v support
Date: Thu, 11 Dec 2014 14:08:08 +0100	[thread overview]
Message-ID: <20141211130807.GA18311@potion.brq.redhat.com> (raw)
In-Reply-To: <1418285221-14256-1-git-send-email-zhang.zhanghailiang@huawei.com>

2014-12-11 16:07+0800, zhanghailiang:
> User space (i.e. QEMU) should be able to check whether KVM
> supports apic-v. User space will use this to decide whether enable
> emulated MSR-based APIC (i.e. hyperv-vapic).

Userspace is able to look at enable_apicv module parameter.
(This decision probably belongs to controls above QEMU.)

Anyway, I haven't thought much about it, so to the patch itself:
- KVM_CAP_VMX_APICV isn't a good name for a capability that doesn't
  require VMX.
- The detection depends on irqchip_in_kernel(), which is awkward.

      parent reply	other threads:[~2014-12-11 13:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-11  8:07 [PATCH] KVM: add KVM_CAP_VMX_APICV to advertise hardware apic-v support zhanghailiang
2014-12-11 11:48 ` Paolo Bonzini
2014-12-11 12:53   ` zhanghailiang
2014-12-11 13:28     ` Radim Krčmář
2014-12-11 17:15     ` Paolo Bonzini
2014-12-17 22:17       ` Stefan Fritsch
2014-12-18  3:37         ` zhanghailiang
2014-12-18  8:30           ` Paolo Bonzini
2014-12-18  8:57             ` Stefan Fritsch
2014-12-18  9:23               ` Paolo Bonzini
2014-12-11 13:08 ` Radim Krčmář [this message]

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=20141211130807.GA18311@potion.brq.redhat.com \
    --to=rkrcmar@redhat.com \
    --cc=gleb@kernel.org \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.huangpeng@huawei.com \
    --cc=zhang.zhanghailiang@huawei.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.