mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Vitaly Kuznetsov <vkuznets@redhat.com>, kvm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, "Radim Krčmář" <rkrcmar@redhat.com>,
	"Joerg Roedel" <joro@8bytes.org>,
	"Jim Mattson" <jmattson@google.com>,
	"Sean Christopherson" <sean.j.christopherson@intel.com>,
	"Roman Kagan" <rkagan@virtuozzo.com>
Subject: Re: [PATCH v2 0/2] KVM: x86: don't announce KVM_CAP_HYPERV_ENLIGHTENED_VMCS when it is unavailable
Date: Tue, 17 Sep 2019 15:29:04 +0200	[thread overview]
Message-ID: <0f3650ef-6a64-b6ab-5370-92e7c4d6cce1@redhat.com> (raw)
In-Reply-To: <20190828075905.24744-1-vkuznets@redhat.com>

On 28/08/19 09:59, Vitaly Kuznetsov wrote:
> It was discovered that hyperv_cpuid test now fails on AMD as it tries to
> enable KVM_CAP_HYPERV_ENLIGHTENED_VMCS which is (wrongfully) reported as
> available.
> 
> Changes since v1:
> - This is a v2 for '[PATCH 0/3] KVM: x86: fix a couple of issues with
>  Enlightened VMCS enablement' renamed as the first patch of the series
>  was already merged.
> - Added Jim's Reviewed-by: to PATCH1
> - Added missing break in PATCH2 [Jim Mattson, Sean Christopherson] 
> 
> Vitaly Kuznetsov (2):
>   KVM: x86: svm: remove unneeded nested_enable_evmcs() hook
>   KVM: x86: announce KVM_CAP_HYPERV_ENLIGHTENED_VMCS support only when
>     it is available
> 
>  arch/x86/kvm/svm.c | 9 +--------
>  arch/x86/kvm/x86.c | 4 +++-
>  2 files changed, 4 insertions(+), 9 deletions(-)
> 

Queued, thanks.

Paolo

      parent reply	other threads:[~2019-09-17 13:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-28  7:59 Vitaly Kuznetsov
2019-08-28  7:59 ` [PATCH v2 1/2] KVM: x86: svm: remove unneeded nested_enable_evmcs() hook Vitaly Kuznetsov
2019-08-28  7:59 ` [PATCH v2 2/2] KVM: x86: announce KVM_CAP_HYPERV_ENLIGHTENED_VMCS support only when it is available Vitaly Kuznetsov
2019-08-28 16:24   ` Jim Mattson
2019-09-17 13:29 ` Paolo Bonzini [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=0f3650ef-6a64-b6ab-5370-92e7c4d6cce1@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jmattson@google.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkagan@virtuozzo.com \
    --cc=rkrcmar@redhat.com \
    --cc=sean.j.christopherson@intel.com \
    --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

all inboxes | Powered by JetHome®