From: Sean Christopherson <seanjc@google.com>
To: Sean Christopherson <seanjc@google.com>,
Paolo Bonzini <pbonzini@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Takahiro Itazuri <itazur@amazon.com>
Subject: Re: [PATCH v3 0/2] KVM: x86: Report actual nent from KVM_GET_CPUID2
Date: Thu, 1 Jun 2023 18:21:51 -0700 [thread overview]
Message-ID: <168565363778.667891.6228323233552429426.b4-ty@google.com> (raw)
In-Reply-To: <20230526210340.2799158-1-seanjc@google.com>
On Fri, 26 May 2023 14:03:38 -0700, Sean Christopherson wrote:
> Essentially v3 of Takahiro's patch. Update cpuid->nent on a successful
> KVM_GET_CPUID2 so that userspace knows exactly how many entries were
> filled. Add a testcase to verify KVM's ABI.
>
> v3:
> - Don't bother updating cpuid->nent in the error path, the data is never
> copied to userspace.
> - Add testcase to cpuid_test
>
> [...]
Applied to kvm-x86 misc, thanks!
[1/2] KVM: x86: Update number of entries for KVM_GET_CPUID2 on success, not failure
https://github.com/kvm-x86/linux/commit/ab322c43cce9
[2/2] KVM: selftests: Extend cpuid_test to verify KVM_GET_CPUID2 "nent" updates
https://github.com/kvm-x86/linux/commit/2c7613131998
--
https://github.com/kvm-x86/linux/tree/next
https://github.com/kvm-x86/linux/tree/fixes
next prev parent reply other threads:[~2023-06-02 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 21:03 Sean Christopherson
2023-05-26 21:03 ` [PATCH v3 1/2] KVM: x86: Update number of entries for KVM_GET_CPUID2 on success, not failure Sean Christopherson
2023-05-26 21:03 ` [PATCH v3 2/2] KVM: selftests: Extend cpuid_test to verify KVM_GET_CPUID2 "nent" updates Sean Christopherson
2023-06-02 1:21 ` Sean Christopherson [this message]
2023-06-02 8:42 ` [PATCH v3 0/2] KVM: x86: Report actual nent from KVM_GET_CPUID2 Takahiro Itazuri
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=168565363778.667891.6228323233552429426.b4-ty@google.com \
--to=seanjc@google.com \
--cc=itazur@amazon.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@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®