From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: jing2.liu@linux.intel.com
Subject: [PATCH 0/5] KVM: cpuid: cleanups, simplify multi-index CPUID leaves
Date: Thu, 4 Jul 2019 16:07:10 +0200 [thread overview]
Message-ID: <20190704140715.31181-1-pbonzini@redhat.com> (raw)
While reviewing the AVX512_BF16, Jing Liu and I noted that the handling of
CPUID leaf 7 is quite messy, and in general the handling of multi-index
CPUID leaves is confusing. These patches clean the code to prepare
for adding CPUID leaf 7 subleaf 1.
Paolo Bonzini (5):
KVM: cpuid: do_cpuid_ent works on a whole CPUID function
KVM: cpuid: extract do_cpuid_7_mask and support multiple subleafs
KVM: cpuid: set struct kvm_cpuid_entry2 flags in do_cpuid_1_ent
KVM: cpuid: rename do_cpuid_1_ent
KVM: cpuid: remove has_leaf_count from struct kvm_cpuid_param
arch/x86/kvm/cpuid.c | 222 ++++++++++++++++++++++++-------------------
1 file changed, 122 insertions(+), 100 deletions(-)
--
2.21.0
next reply other threads:[~2019-07-04 14:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-04 14:07 Paolo Bonzini [this message]
2019-07-04 14:07 ` [PATCH 1/5] KVM: cpuid: do_cpuid_ent works on a whole CPUID function Paolo Bonzini
2019-07-08 7:05 ` Jing Liu
2019-07-04 14:07 ` [PATCH 2/5] KVM: cpuid: extract do_cpuid_7_mask and support multiple subleafs Paolo Bonzini
2019-07-08 7:07 ` Jing Liu
2019-07-10 6:30 ` Paolo Bonzini
2019-07-10 7:32 ` Jing Liu
2019-07-10 7:48 ` Paolo Bonzini
2019-07-04 14:07 ` [PATCH 3/5] KVM: cpuid: set struct kvm_cpuid_entry2 flags in do_cpuid_1_ent Paolo Bonzini
2019-07-04 14:07 ` [PATCH 4/5] KVM: cpuid: rename do_cpuid_1_ent Paolo Bonzini
2019-07-04 14:07 ` [PATCH 5/5] KVM: cpuid: remove has_leaf_count from struct kvm_cpuid_param Paolo Bonzini
2019-07-08 7:09 ` Jing Liu
2019-07-10 6:34 ` Paolo Bonzini
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=20190704140715.31181-1-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=jing2.liu@linux.intel.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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®