All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: David Woodhouse <dwmw2@infradead.org>, kvm@vger.kernel.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
	Ankur Arora <ankur.a.arora@oracle.com>,
	Joao Martins <joao.m.martins@oracle.com>,
	Boris Ostrovsky <boris.ostrovsky@oracle.com>,
	Sean Christopherson <seanjc@google.com>,
	graf@amazon.com, iaslan@amazon.de, pdurrant@amazon.com,
	aagch@amazon.com, fandree@amazon.com
Subject: Re: [PATCH v3 02/17] KVM: x86/xen: fix Xen hypercall page msr handling
Date: Mon, 14 Dec 2020 22:27:19 +0100	[thread overview]
Message-ID: <87czzcw020.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <20201214083905.2017260-3-dwmw2@infradead.org>

David Woodhouse <dwmw2@infradead.org> writes:

> From: Joao Martins <joao.m.martins@oracle.com>
>
> Xen usually places its MSR at 0x40000000 or 0x40000200 depending on
> whether it is running in viridian mode or not. Note that this is not
> ABI guaranteed, so it is possible for Xen to advertise the MSR some
> place else.
>
> Given the way xen_hvm_config() is handled, if the former address is
> selected, this will conflict with Hyper-V's MSR
> (HV_X64_MSR_GUEST_OS_ID) which unconditionally uses the same address.
>
> Given that the MSR location is arbitrary, move the xen_hvm_config()
> handling to the top of kvm_set_msr_common() before falling through.
>

In case we're making MSR 0x40000000 something different from
HV_X64_MSR_GUEST_OS_ID we can and probably should disable Hyper-V
emulation in KVM completely -- or how else is it going to work?

> Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
> Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
> ---
>  arch/x86/kvm/x86.c | 5 +++--
>  1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/x86/kvm/x86.c b/arch/x86/kvm/x86.c
> index c7f1ba21212e..13ba4a64f748 100644
> --- a/arch/x86/kvm/x86.c
> +++ b/arch/x86/kvm/x86.c
> @@ -3001,6 +3001,9 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
>  	u32 msr = msr_info->index;
>  	u64 data = msr_info->data;
>  
> +	if (msr && (msr == vcpu->kvm->arch.xen_hvm_config.msr))
> +		return xen_hvm_config(vcpu, data);
> +

Can we generalize this maybe? E.g. before handling KVM and architectural
MSRs we check that the particular MSR is not overriden by an emulated
hypervisor, 

e.g.
	if (kvm_emulating_hyperv(kvm) && kvm_hyperv_msr_overriden(kvm,msr)
		return kvm_hyperv_handle_msr(kvm, msr);
	if (kvm_emulating_xen(kvm) && kvm_xen_msr_overriden(kvm,msr)
		return kvm_xen_handle_msr(kvm, msr);

	switch (msr) {
		...

>  	switch (msr) {
>  	case MSR_AMD64_NB_CFG:
>  	case MSR_IA32_UCODE_WRITE:
> @@ -3288,8 +3291,6 @@ int kvm_set_msr_common(struct kvm_vcpu *vcpu, struct msr_data *msr_info)
>  		vcpu->arch.msr_misc_features_enables = data;
>  		break;
>  	default:
> -		if (msr && (msr == vcpu->kvm->arch.xen_hvm_config.msr))
> -			return xen_hvm_config(vcpu, data);
>  		if (kvm_pmu_is_valid_msr(vcpu, msr))
>  			return kvm_pmu_set_msr(vcpu, msr_info);
>  		return KVM_MSR_RET_INVALID;

-- 
Vitaly


  reply	other threads:[~2020-12-14 21:28 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-14  8:38 [PATCH v3 00/17] KVM: Add minimal support for Xen HVM guests David Woodhouse
2020-12-14  8:38 ` [PATCH v3 01/17] KVM: Fix arguments to kvm_{un,}map_gfn() David Woodhouse
2020-12-14 21:13   ` Vitaly Kuznetsov
2020-12-14 21:21     ` David Woodhouse
2020-12-14 21:41       ` Vitaly Kuznetsov
2020-12-14 21:45         ` David Woodhouse
2020-12-15 12:07           ` Vitaly Kuznetsov
2020-12-15 12:45             ` David Woodhouse
2020-12-14  8:38 ` [PATCH v3 02/17] KVM: x86/xen: fix Xen hypercall page msr handling David Woodhouse
2020-12-14 21:27   ` Vitaly Kuznetsov [this message]
2020-12-14 21:35     ` David Woodhouse
2020-12-14 21:44       ` Vitaly Kuznetsov
2020-12-14 21:48         ` David Woodhouse
2020-12-14 22:22           ` Vitaly Kuznetsov
2020-12-14 22:41             ` David Woodhouse
2020-12-15 12:10               ` Vitaly Kuznetsov
2020-12-23  8:35   ` Christoph Hellwig
2020-12-14  8:38 ` [PATCH v3 03/17] KVM: x86/xen: intercept xen hypercalls if enabled David Woodhouse
2020-12-23  8:36   ` Christoph Hellwig
2020-12-23 10:51     ` David Woodhouse
2020-12-14  8:38 ` [PATCH v3 04/17] KVM: x86/xen: Fix coexistence of Xen and Hyper-V hypercalls David Woodhouse
2020-12-14  8:38 ` [PATCH v3 05/17] KVM: x86/xen: add KVM_XEN_HVM_SET_ATTR/KVM_XEN_HVM_GET_ATTR David Woodhouse
2020-12-14  8:38 ` [PATCH v3 06/17] KVM: x86/xen: latch long_mode when hypercall page is set up David Woodhouse
2020-12-14  8:38 ` [PATCH v3 07/17] KVM: x86/xen: add definitions of compat_shared_info, compat_vcpu_info David Woodhouse
2020-12-14  8:38 ` [PATCH v3 08/17] KVM: x86/xen: register shared_info page David Woodhouse
2020-12-14 10:45   ` Joao Martins
2020-12-14 11:30     ` Joao Martins
2020-12-14 12:04       ` David Woodhouse
2020-12-14 12:02     ` David Woodhouse
2020-12-14 12:53       ` Joao Martins
2020-12-14 15:05         ` David Woodhouse
2020-12-14  8:38 ` [PATCH v3 09/17] xen: add wc_sec_hi to struct shared_info David Woodhouse
2020-12-14  8:38 ` [PATCH v3 10/17] KVM: x86/xen: update wallclock region David Woodhouse
2020-12-14  8:38 ` [PATCH v3 11/17] KVM: x86/xen: register vcpu info David Woodhouse
2020-12-14 10:48   ` Joao Martins
2020-12-14  8:39 ` [PATCH v3 12/17] KVM: x86/xen: setup pvclock updates David Woodhouse
2020-12-14 13:29   ` Joao Martins
2020-12-14 14:58     ` David Woodhouse
2020-12-14 15:20       ` Joao Martins
2020-12-14 15:40         ` David Woodhouse
2020-12-14  8:39 ` [PATCH v3 13/17] KVM: x86/xen: register vcpu time info region David Woodhouse
2020-12-14 10:55   ` Joao Martins
2020-12-14 12:03     ` David Woodhouse
2020-12-14  8:39 ` [PATCH v3 14/17] KVM: x86/xen: register runstate info David Woodhouse
2020-12-14 11:10   ` Joao Martins
2020-12-14 15:47     ` David Woodhouse
2020-12-14  8:39 ` [PATCH v3 15/17] KVM: x86: declare Xen HVM shared info capability and add test case David Woodhouse
2020-12-14  8:39 ` [PATCH v3 16/17] KVM: Add documentation for Xen hypercall and shared_info updates David Woodhouse
2020-12-14  8:39 ` [PATCH v3 17/17] KVM: x86/xen: Add event channel interrupt vector upcall David Woodhouse
2020-12-14 13:19   ` Joao Martins
2020-12-14 13:32     ` Durrant, Paul
2020-12-14 14:57     ` David Woodhouse
2020-12-14 15:13       ` Joao Martins

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=87czzcw020.fsf@vitty.brq.redhat.com \
    --to=vkuznets@redhat.com \
    --cc=aagch@amazon.com \
    --cc=ankur.a.arora@oracle.com \
    --cc=boris.ostrovsky@oracle.com \
    --cc=dwmw2@infradead.org \
    --cc=fandree@amazon.com \
    --cc=graf@amazon.com \
    --cc=iaslan@amazon.de \
    --cc=joao.m.martins@oracle.com \
    --cc=kvm@vger.kernel.org \
    --cc=pbonzini@redhat.com \
    --cc=pdurrant@amazon.com \
    --cc=seanjc@google.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.