From: Vitaly Kuznetsov <vkuznets@redhat.com>
To: Liran Alon <liran.alon@oracle.com>
Cc: kvm@vger.kernel.org, "Paolo Bonzini" <pbonzini@redhat.com>,
"Radim Krčmář" <rkrcmar@redhat.com>,
"Roman Kagan" <rkagan@virtuozzo.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] x86/kvm/hyper-v: tweak HYPERV_CPUID_ENLIGHTMENT_INFO
Date: Thu, 24 Jan 2019 18:39:21 +0100 [thread overview]
Message-ID: <8736pigdkm.fsf@vitty.brq.redhat.com> (raw)
In-Reply-To: <805B7B08-734E-4A96-AF98-D33065C59105@oracle.com>
Liran Alon <liran.alon@oracle.com> writes:
>> On 24 Jan 2019, at 19:15, Vitaly Kuznetsov <vkuznets@redhat.com> wrote:
>>
>> We shouldn't probably be suggesting using Enlightened VMCS when it's not
>> enabled (not supported from guest's point of view). System reset through
>> synthetic MSR is not recommended neither by genuine Hyper-V nor my QEMU.
>>
>> Windows seems to be fine either way but let's be consistent.
>>
>> Fixes: 2bc39970e932 ("x86/kvm/hyper-v: Introduce KVM_GET_SUPPORTED_HV_CPUID")
>> Signed-off-by: Vitaly Kuznetsov <vkuznets@redhat.com>
>> ---
>> arch/x86/kvm/hyperv.c | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/arch/x86/kvm/hyperv.c b/arch/x86/kvm/hyperv.c
>> index ac44a681f065..4730fcaa70cf 100644
>> --- a/arch/x86/kvm/hyperv.c
>> +++ b/arch/x86/kvm/hyperv.c
>> @@ -1847,11 +1847,11 @@ int kvm_vcpu_ioctl_get_hv_cpuid(struct kvm_vcpu *vcpu, struct kvm_cpuid2 *cpuid,
>> case HYPERV_CPUID_ENLIGHTMENT_INFO:
>> ent->eax |= HV_X64_REMOTE_TLB_FLUSH_RECOMMENDED;
>> ent->eax |= HV_X64_APIC_ACCESS_RECOMMENDED;
>> - ent->eax |= HV_X64_SYSTEM_RESET_RECOMMENDED;
>> ent->eax |= HV_X64_RELAXED_TIMING_RECOMMENDED;
>> ent->eax |= HV_X64_CLUSTER_IPI_RECOMMENDED;
>> ent->eax |= HV_X64_EX_PROCESSOR_MASKS_RECOMMENDED;
>> - ent->eax |= HV_X64_ENLIGHTENED_VMCS_RECOMMENDED;
>> + if (evmcs_ver)
>> + ent->eax |= HV_X64_ENLIGHTENED_VMCS_RECOMMENDED;
>>
>> /*
>> * Default number of spinlock retry attempts, matches
>> --
>> 2.20.1
>>
>
> Seems to me that there are 2 unrelated separated patches here. Why not
> split them?
They seem to be too small :-) No problem, I'll split them up in v2.
> For content itself: Reviewed-by: Liran Alon <liran.alon@oracle.com>
>
Thanks!
--
Vitaly
next prev parent reply other threads:[~2019-01-24 17:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-24 17:15 [PATCH] x86/kvm/hyper-v: tweak HYPERV_CPUID_ENLIGHTMENT_INFO Vitaly Kuznetsov
2019-01-24 17:28 ` Liran Alon
2019-01-24 17:39 ` Vitaly Kuznetsov [this message]
2019-01-24 17:41 ` Liran Alon
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=8736pigdkm.fsf@vitty.brq.redhat.com \
--to=vkuznets@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liran.alon@oracle.com \
--cc=pbonzini@redhat.com \
--cc=rkagan@virtuozzo.com \
--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