From: Paolo Bonzini <pbonzini@redhat.com>
To: lantianyu1986@gmail.com, rth@twiddle.net, ehabkost@redhat.com,
mtosatti@redhat.com, vkuznets@redhat.com,
Roman Kagan <rkagan@virtuozzo.com>
Cc: Tianyu Lan <Tianyu.Lan@microsoft.com>,
qemu-devel@nongnu.org, kvm@vger.kernel.org
Subject: Re: [PATCH V3 2/2] target/i386/kvm: Add Hyper-V direct tlb flush support
Date: Tue, 22 Oct 2019 19:04:11 +0200 [thread overview]
Message-ID: <7de12770-271e-d386-a105-d53b50aa731f@redhat.com> (raw)
In-Reply-To: <20191016130725.5045-3-Tianyu.Lan@microsoft.com>
On 16/10/19 15:07, lantianyu1986@gmail.com wrote:
> From: Tianyu Lan <Tianyu.Lan@microsoft.com>
>
> Hyper-V direct tlb flush targets KVM on Hyper-V guest.
> Enable direct TLB flush for its guests meaning that TLB
> flush hypercalls are handled by Level 0 hypervisor (Hyper-V)
> bypassing KVM in Level 1. Due to the different ABI for hypercall
> parameters between Hyper-V and KVM, KVM capabilities should be
> hidden when enable Hyper-V direct tlb flush otherwise KVM
> hypercalls may be intercepted by Hyper-V. Add new parameter
> "hv-direct-tlbflush". Check expose_kvm and Hyper-V tlb flush
> capability status before enabling the feature.
>
> Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
> ---
> Change sicne v2:
> - Update new feature description and name.
> - Change failure print log.
>
> Change since v1:
> - Add direct tlb flush's Hyper-V property and use
> hv_cpuid_check_and_set() to check the dependency of tlbflush
> feature.
> - Make new feature work with Hyper-V passthrough mode.
> ---
> docs/hyperv.txt | 10 ++++++++++
> target/i386/cpu.c | 2 ++
> target/i386/cpu.h | 1 +
> target/i386/kvm.c | 24 ++++++++++++++++++++++++
> 4 files changed, 37 insertions(+)
>
> diff --git a/docs/hyperv.txt b/docs/hyperv.txt
> index 8fdf25c829..140a5c7e44 100644
> --- a/docs/hyperv.txt
> +++ b/docs/hyperv.txt
> @@ -184,6 +184,16 @@ enabled.
>
> Requires: hv-vpindex, hv-synic, hv-time, hv-stimer
>
> +3.18. hv-direct-tlbflush
> +=======================
> +Enable direct TLB flush for KVM when it is running as a nested
> +hypervisor on top Hyper-V. When enabled, TLB flush hypercalls from L2
> +guests are being passed through to L0 (Hyper-V) for handling. Due to ABI
> +differences between Hyper-V and KVM hypercalls, L2 guests will not be
> +able to issue KVM hypercalls (as those could be mishanled by L0
> +Hyper-V), this requires KVM hypervisor signature to be hidden.
> +
> +Requires: hv-tlbflush, -kvm
>
> 4. Development features
> ========================
> diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> index 44f1bbdcac..7bc7fee512 100644
> --- a/target/i386/cpu.c
> +++ b/target/i386/cpu.c
> @@ -6156,6 +6156,8 @@ static Property x86_cpu_properties[] = {
> HYPERV_FEAT_IPI, 0),
> DEFINE_PROP_BIT64("hv-stimer-direct", X86CPU, hyperv_features,
> HYPERV_FEAT_STIMER_DIRECT, 0),
> + DEFINE_PROP_BIT64("hv-direct-tlbflush", X86CPU, hyperv_features,
> + HYPERV_FEAT_DIRECT_TLBFLUSH, 0),
> DEFINE_PROP_BOOL("hv-passthrough", X86CPU, hyperv_passthrough, false),
>
> DEFINE_PROP_BOOL("check", X86CPU, check_cpuid, true),
> diff --git a/target/i386/cpu.h b/target/i386/cpu.h
> index eaa5395aa5..3cb105f7d6 100644
> --- a/target/i386/cpu.h
> +++ b/target/i386/cpu.h
> @@ -907,6 +907,7 @@ typedef uint64_t FeatureWordArray[FEATURE_WORDS];
> #define HYPERV_FEAT_EVMCS 12
> #define HYPERV_FEAT_IPI 13
> #define HYPERV_FEAT_STIMER_DIRECT 14
> +#define HYPERV_FEAT_DIRECT_TLBFLUSH 15
>
> #ifndef HYPERV_SPINLOCK_NEVER_RETRY
> #define HYPERV_SPINLOCK_NEVER_RETRY 0xFFFFFFFF
> diff --git a/target/i386/kvm.c b/target/i386/kvm.c
> index 11b9c854b5..043b66ab22 100644
> --- a/target/i386/kvm.c
> +++ b/target/i386/kvm.c
> @@ -900,6 +900,10 @@ static struct {
> },
> .dependencies = BIT(HYPERV_FEAT_STIMER)
> },
> + [HYPERV_FEAT_DIRECT_TLBFLUSH] = {
> + .desc = "direct paravirtualized TLB flush (hv-direct-tlbflush)",
> + .dependencies = BIT(HYPERV_FEAT_TLBFLUSH)
> + },
> };
>
> static struct kvm_cpuid2 *try_get_hv_cpuid(CPUState *cs, int max)
> @@ -1224,6 +1228,7 @@ static int hyperv_handle_properties(CPUState *cs,
> r |= hv_cpuid_check_and_set(cs, cpuid, HYPERV_FEAT_EVMCS);
> r |= hv_cpuid_check_and_set(cs, cpuid, HYPERV_FEAT_IPI);
> r |= hv_cpuid_check_and_set(cs, cpuid, HYPERV_FEAT_STIMER_DIRECT);
> + r |= hv_cpuid_check_and_set(cs, cpuid, HYPERV_FEAT_DIRECT_TLBFLUSH);
>
> /* Additional dependencies not covered by kvm_hyperv_properties[] */
> if (hyperv_feat_enabled(cpu, HYPERV_FEAT_SYNIC) &&
> @@ -1243,6 +1248,25 @@ static int hyperv_handle_properties(CPUState *cs,
> goto free;
> }
>
> + if (hyperv_feat_enabled(cpu, HYPERV_FEAT_DIRECT_TLBFLUSH) ||
> + cpu->hyperv_passthrough) {
> + if (!cpu->expose_kvm) {
> + r = kvm_vcpu_enable_cap(cs, KVM_CAP_HYPERV_DIRECT_TLBFLUSH, 0, 0);
> + if (hyperv_feat_enabled(cpu, HYPERV_FEAT_DIRECT_TLBFLUSH) && r) {
> + fprintf(stderr,
> + "Hyper-V %s is not supported by kernel\n",
> + kvm_hyperv_properties[HYPERV_FEAT_DIRECT_TLBFLUSH].desc);
> + return -ENOSYS;
> + }
> + } else if (!cpu->hyperv_passthrough) {
> + fprintf(stderr,
> + "Hyper-V %s requires KVM hypervisor signature "
> + "to be hidden (-kvm).\n",
> + kvm_hyperv_properties[HYPERV_FEAT_DIRECT_TLBFLUSH].desc);
> + return -ENOSYS;
> + }
> + }
> +
> if (cpu->hyperv_passthrough) {
> /* We already copied all feature words from KVM as is */
> r = cpuid->nent;
>
Queued, thanks. Patch 1 is not needed anymore.
Paolo
next prev parent reply other threads:[~2019-10-22 17:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:07 [PATCH V3 0/2] target/i386/kvm: Add Hyper-V direct tlb flush support lantianyu1986
2019-10-16 13:07 ` [PATCH V3 1/2] linux headers: update against Linux 5.4-rc2 lantianyu1986
[not found] ` <20191016130725.5045-3-Tianyu.Lan@microsoft.com>
2019-10-22 17:04 ` Paolo Bonzini [this message]
2019-10-22 20:14 ` [PATCH V3 2/2] target/i386/kvm: Add Hyper-V direct tlb flush support Roman Kagan
2019-10-23 7:16 ` 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=7de12770-271e-d386-a105-d53b50aa731f@redhat.com \
--to=pbonzini@redhat.com \
--cc=Tianyu.Lan@microsoft.com \
--cc=ehabkost@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=lantianyu1986@gmail.com \
--cc=mtosatti@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkagan@virtuozzo.com \
--cc=rth@twiddle.net \
--cc=vkuznets@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;
as well as URLs for NNTP newsgroup(s).