From: Eduardo Habkost <ehabkost@redhat.com>
To: Wanpeng Li <kernellwp@gmail.com>
Cc: linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>
Subject: Re: [PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint
Date: Fri, 9 Feb 2018 12:31:17 -0200 [thread overview]
Message-ID: <20180209143117.GL13981@localhost.localdomain> (raw)
In-Reply-To: <1518185725-69559-1-git-send-email-wanpengli@tencent.com>
On Fri, Feb 09, 2018 at 06:15:25AM -0800, Wanpeng Li wrote:
> From: Wanpeng Li <wanpengli@tencent.com>
>
> Add KVM_HINTS_DEDICATED performance hint, guest checks this feature bit
> to determine if they run on dedicated vCPUs, allowing optimizations such
> as usage of qspinlocks.
>
> Cc: Paolo Bonzini <pbonzini@redhat.com>
> Cc: Radim Krčmář <rkrcmar@redhat.com>
> Cc: Eduardo Habkost <ehabkost@redhat.com>
> Signed-off-by: Wanpeng Li <wanpengli@tencent.com>
[...]
> + [FEAT_KVM_HINTS] = {
> + .feat_names = {
> + "hint-dedicated", NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + NULL, NULL, NULL, NULL,
> + },
> + .cpuid_eax = KVM_CPUID_FEATURES, .cpuid_reg = R_EDX,
> + .tcg_features = TCG_KVM_FEATURES,
> + },
Do you have a pointer to the KVM patch that adds this bit to
Documentation/virtual/kvm/cpuid.txt? I would like to wait until
the KVM CPUID docs are updated before applying the patch to QEMU.
--
Eduardo
next prev parent reply other threads:[~2018-02-09 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 14:15 [PATCH v2] target-i386: add KVM_HINTS_DEDICATED performance hint Wanpeng Li
2018-02-09 14:31 ` Eduardo Habkost [this message]
2018-02-09 14:52 ` Wanpeng Li
2018-02-28 12:31 ` Wanpeng Li
2018-02-28 15:05 ` Paolo Bonzini
2018-03-09 14:16 ` Eduardo Habkost
2018-03-10 1:43 ` Wanpeng Li
2018-04-10 9:13 ` Wanpeng Li
2018-04-10 11:57 ` Eduardo Habkost
2018-04-10 12:04 ` Paolo Bonzini
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=20180209143117.GL13981@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=kernellwp@gmail.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rkrcmar@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox