From: Robert Hoo <robert.hu@linux.intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: robert.hu@intel.com, robert.hu@linux.intel.com, rth@twiddle.net,
ehabkost@redhat.com, thomas.lendacky@amd.com,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 1/2] i386: remove the new CPUID 'PCONFIG' from Icelake-Server CPU model
Date: Thu, 20 Dec 2018 20:50:52 +0800 [thread overview]
Message-ID: <1545310252.44118.5.camel@linux.intel.com> (raw)
In-Reply-To: <e1b012da-7aac-1063-35ae-0ab3c4c5eb4b@redhat.com>
On Thu, 2018-12-20 at 13:38 +0100, Paolo Bonzini wrote:
> On 20/12/18 01:18, Robert Hoo wrote:
> > On Wed, 2018-12-19 at 14:01 +0000, Daniel P. Berrangé wrote:
> > > On Wed, Dec 19, 2018 at 09:44:40PM +0800, Robert Hoo wrote:
> > > > Signed-off-by: Robert Hoo <robert.hu@linux.intel.com>
> > > > ---
> > > > target/i386/cpu.c | 3 +--
> > > > 1 file changed, 1 insertion(+), 2 deletions(-)
> > > >
> > > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > > index 677a3bd..b6113d0 100644
> > > > --- a/target/i386/cpu.c
> > > > +++ b/target/i386/cpu.c
> > > > @@ -2613,8 +2613,7 @@ static X86CPUDefinition
> > > > builtin_x86_defs[] =
> > > > {
> > > > CPUID_7_0_ECX_AVX512VNNI |
> > > > CPUID_7_0_ECX_AVX512BITALG
> > > > >
> > > >
> > > > CPUID_7_0_ECX_AVX512_VPOPCNTDQ |
> > > > CPUID_7_0_ECX_LA57,
> > > > .features[FEAT_7_0_EDX] =
> > > > - CPUID_7_0_EDX_PCONFIG | CPUID_7_0_EDX_SPEC_CTRL |
> > > > - CPUID_7_0_EDX_SPEC_CTRL_SSBD,
> > > > + CPUID_7_0_EDX_SPEC_CTRL |
> > > > CPUID_7_0_EDX_SPEC_CTRL_SSBD,
> > > > /* Missing: XSAVES (not supported by some Linux
> > > > versions,
> > > > * including v4.1 to v4.12).
> > > > * KVM doesn't yet expose any XSAVES state save
> > > > component,
> > >
> > > This was shipped in QEMU 3.1.0, so I don't think we can
> > > unconditionally
> > > remove it like this without breaking CPU model migration compat.
> > >
> >
> > I think the sooner, the better. Take the time window that Icelake
> > CPU
> > model has just shipped with QEMU 3.1.0 and is not publicly/widely
> > used
> > yet.
>
> We should still leave it in the 3.1 machine types. I've just sent a
> patch to do the same with MPX.
>
I took a look your patch of "Disable MPX support on named CPU models".
Seems you do the same as I do to PCONFIG. So you agree with my above
patch?:-)
I won't object that keep it in 3.1 machine type as you do to MPX.
> Paolo
>
next prev parent reply other threads:[~2018-12-20 12:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-19 13:44 [Qemu-devel] [PATCH 0/2] Revert exposure of PCONFIG to guest Robert Hoo
2018-12-19 13:44 ` [Qemu-devel] [PATCH 1/2] i386: remove the new CPUID 'PCONFIG' from Icelake-Server CPU model Robert Hoo
2018-12-19 14:01 ` Daniel P. Berrangé
2018-12-20 0:18 ` Robert Hoo
2018-12-20 12:38 ` Paolo Bonzini
2018-12-20 12:50 ` Robert Hoo [this message]
2018-12-20 13:06 ` Paolo Bonzini
2018-12-21 6:27 ` Paolo Bonzini
2018-12-21 14:04 ` Robert Hoo
2018-12-21 15:03 ` Paolo Bonzini
2018-12-22 0:58 ` Robert Hoo
2018-12-19 13:44 ` [Qemu-devel] [PATCH 2/2] Revert "i386: Add CPUID bit for PCONFIG" Robert Hoo
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=1545310252.44118.5.camel@linux.intel.com \
--to=robert.hu@linux.intel.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=rth@twiddle.net \
--cc=thomas.lendacky@amd.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).