From: Paolo Bonzini <pbonzini@redhat.com>
To: Xiaoyao Li <xiaoyao.li@intel.com>,
Richard Henderson <rth@twiddle.net>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: Cathy Zhang <cathy.zhang@intel.com>, qemu-devel@nongnu.org
Subject: Re: [PATCH 0/2] Fix Cooperlake CPU model
Date: Tue, 7 Jan 2020 14:31:55 +0100 [thread overview]
Message-ID: <93c9cc8c-09ec-d13f-f012-edf86fd945ab@redhat.com> (raw)
In-Reply-To: <20191225063018.20038-1-xiaoyao.li@intel.com>
On 25/12/19 07:30, Xiaoyao Li wrote:
> Current Cooperlake CPU model lacks VMX features which are introduced by Paolo
> several months ago, and it also lacks 2 security features in
> MSR_IA32_ARCH_CAPABILITIES disclosed recently.
>
> Xiaoyao Li (2):
> target/i386: Add new bit definitions of MSR_IA32_ARCH_CAPABILITIES
> target/i386: Add missed features to Cooperlake CPU model
>
> target/i386/cpu.c | 51 ++++++++++++++++++++++++++++++++++++++++++++++-
> target/i386/cpu.h | 13 +++++++-----
> 2 files changed, 58 insertions(+), 6 deletions(-)
>
Queued, thanks.
Paolo
next prev parent reply other threads:[~2020-01-07 14:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-25 6:30 [PATCH 0/2] Fix Cooperlake CPU model Xiaoyao Li
2019-12-25 6:30 ` [PATCH 1/2] target/i386: Add new bit definitions of MSR_IA32_ARCH_CAPABILITIES Xiaoyao Li
2019-12-25 6:30 ` [PATCH 2/2] target/i386: Add missed features to Cooperlake CPU model Xiaoyao Li
2020-08-24 22:07 ` Eduardo Habkost
2020-08-25 0:20 ` Xiaoyao Li
2020-08-25 14:01 ` Eduardo Habkost
2020-08-26 2:43 ` Xiaoyao Li
2020-01-07 13:31 ` Paolo Bonzini [this message]
2020-03-16 1:39 ` [PATCH 0/2] Fix " Zhang, Cathy
2020-03-16 8:41 ` Paolo Bonzini
2020-03-16 10:19 ` Zhang, Cathy
2020-03-16 10:24 ` Paolo Bonzini
2020-03-16 11:43 ` Zhang, Cathy
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=93c9cc8c-09ec-d13f-f012-edf86fd945ab@redhat.com \
--to=pbonzini@redhat.com \
--cc=cathy.zhang@intel.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=xiaoyao.li@intel.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;
as well as URLs for NNTP newsgroup(s).