From: Xiaoyao Li <xiaoyao.li@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>,
Marcelo Tosatti <mtosatti@redhat.com>
Cc: qemu-devel@nongnu.org, xiaoyao.li@intel.com
Subject: [PATCH 0/2] i386/cpuid: Minor fixes for CPUID leaf 1f setup
Date: Tue, 12 Jul 2022 10:12:47 +0800 [thread overview]
Message-ID: <20220712021249.3227256-1-xiaoyao.li@intel.com> (raw)
The issue that fixed by Patch 1 looks fatal though it doesn't appear on
KVM because KVM always searches with assending order and hit with the
correct cpuid leaf 0.
Patch 2 removes the wrong constraint on CPUID leaf 1f
Xiaoyao Li (2):
i386/cpuid: Decrease cpuid_i when skipping CPUID leaf 1F
i386/cpuid: Remove subleaf constraint on CPUID leaf 1F
target/i386/kvm/kvm.c | 5 +----
1 file changed, 1 insertion(+), 4 deletions(-)
--
2.27.0
next reply other threads:[~2022-07-12 2:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 2:12 Xiaoyao Li [this message]
2022-07-12 2:12 ` [PATCH 1/2] i386/cpuid: Decrease cpuid_i when skipping CPUID leaf 1F Xiaoyao Li
2022-07-12 2:12 ` [PATCH 2/2] i386/cpuid: Remove subleaf constraint on " Xiaoyao Li
2022-11-02 0:49 ` [PATCH 0/2] i386/cpuid: Minor fixes for CPUID leaf 1f setup Xiaoyao Li
2023-06-07 6:33 ` Xiaoyao Li
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=20220712021249.3227256-1-xiaoyao.li@intel.com \
--to=xiaoyao.li@intel.com \
--cc=mtosatti@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).