From: Paolo Bonzini <pbonzini@redhat.com>
To: "Robert Hoo" <robert.hu@linux.intel.com>,
"Daniel P. Berrangé" <berrange@redhat.com>
Cc: thomas.lendacky@amd.com, ehabkost@redhat.com,
qemu-devel@nongnu.org, robert.hu@intel.com, rth@twiddle.net
Subject: Re: [Qemu-devel] [PATCH 1/2] i386: remove the new CPUID 'PCONFIG' from Icelake-Server CPU model
Date: Fri, 21 Dec 2018 07:27:36 +0100 [thread overview]
Message-ID: <5ee7dd18-e70c-e654-25ee-e700a8174ee9@redhat.com> (raw)
In-Reply-To: <1545310252.44118.5.camel@linux.intel.com>
On 20/12/18 13:50, Robert Hoo wrote:
> On Thu, 2018-12-20 at 13:38 +0100, Paolo Bonzini wrote:
>> On 20/12/18 01:18, Robert Hoo wrote:
>>> 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.
Sorry Robert, I changed my mind. If no hypervisor exists that enables
PCONFIG for guests (using the PCONFIG_ENABLE processor control),
effectively no one can ever have used it. We should disable it in all
machine types and Cc qemu-stable.
In fact, the same is true for INTEL_PT, which is not supported by any
released kernel version and, even is going to be available only with a
module parameter when it will be.
This is not the same as MPX, which did work even though nobody was
probably using it.
So this series is correct and I will follow up with one for INTEL_PT;
however, this begs the question of how the patches are being tested.
Paolo
next prev parent reply other threads:[~2018-12-21 6:27 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
2018-12-20 13:06 ` Paolo Bonzini
2018-12-21 6:27 ` Paolo Bonzini [this message]
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=5ee7dd18-e70c-e654-25ee-e700a8174ee9@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@intel.com \
--cc=robert.hu@linux.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).