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: [PATCH v3 0/2] KVM: x86: Report actual nent from KVM_GET_CPUID2
Date: Fri, 26 May 2023 14:03:38 -0700 [thread overview]
Message-ID: <20230526210340.2799158-1-seanjc@google.com> (raw)
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
v2: https://lore.kernel.org/all/20230413175844.21760-1-itazur@amazon.com
v1: https://lore.kernel.org/all/20230410141820.57328-1-itazur@amazon.com
Sean Christopherson (2):
KVM: x86: Update number of entries for KVM_GET_CPUID2 on success, not
failure
KVM: selftests: Extend cpuid_test to verify KVM_GET_CPUID2 "nent"
updates
arch/x86/kvm/cpuid.c | 13 ++++--------
.../testing/selftests/kvm/x86_64/cpuid_test.c | 21 +++++++++++++++++++
2 files changed, 25 insertions(+), 9 deletions(-)
base-commit: b9846a698c9aff4eb2214a06ac83638ad098f33f
--
2.41.0.rc0.172.g3f132b7071-goog
next reply other threads:[~2023-05-26 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 21:03 Sean Christopherson [this message]
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 ` [PATCH v3 0/2] KVM: x86: Report actual nent from KVM_GET_CPUID2 Sean Christopherson
2023-06-02 8:42 ` 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=20230526210340.2799158-1-seanjc@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®