From: Robert Hoo <robert.hu@linux.intel.com>
To: "Paolo Bonzini" <pbonzini@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-devel@nongnu.org, luwei.kang@intel.com
Cc: robert.hu@intel.com, robert.hu@linux.intel.com, qemu-stable@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] i386: remove the 'INTEL_PT' CPUID bit from named CPU models
Date: Sat, 22 Dec 2018 09:01:54 +0800 [thread overview]
Message-ID: <1545440514.44118.11.camel@linux.intel.com> (raw)
In-Reply-To: <faa89439-18ae-931b-54c7-212b7dea0e48@redhat.com>
On Fri, 2018-12-21 at 16:27 +0100, Paolo Bonzini wrote:
> On 21/12/18 16:22, Philippe Mathieu-Daudé wrote:
> > Hi Paolo,
> >
> > On 12/21/18 7:30 AM, Paolo Bonzini wrote:
> > > From: Robert Hoo <robert.hu@linux.intel.com>
> > >
> > > Processor tracing is not yet implemented for KVM and it will be
> > > an
> > > opt in feature requiring a special module parameter.
> > > Disable it, because it is wrong to enable it by default and
> > > it is impossible that no one has ever used it.
> > >
> > > Cc: qemu-stable@nongnu.org
> >
> > Does this patch misses Robert S-o-b?
> > Signed-off-by: Robert Hoo <robert.hu@linux.intel.com>
Paolo's right. It didn't come from me.
>
> No, the author is wrong, it should be me. "git commit -c" apparently
> copies the author from the original commit.
>
> Paolo
Hi Paolo, would you hold on INTEL_PT removal for a moment? I think I
need Luwei's double confirm.
(Added him in receiver list.)
>
> > > Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
> > > ---
> > > target/i386/cpu.c | 8 +++-----
> > > 1 file changed, 3 insertions(+), 5 deletions(-)
> > >
> > > diff --git a/target/i386/cpu.c b/target/i386/cpu.c
> > > index dae46f0319..9c54c41e7a 100644
> > > --- a/target/i386/cpu.c
> > > +++ b/target/i386/cpu.c
> > > @@ -2493,8 +2493,7 @@ static X86CPUDefinition builtin_x86_defs[]
> > > = {
> > > CPUID_7_0_EBX_SMAP | CPUID_7_0_EBX_CLWB |
> > > CPUID_7_0_EBX_AVX512F | CPUID_7_0_EBX_AVX512DQ |
> > > CPUID_7_0_EBX_AVX512BW | CPUID_7_0_EBX_AVX512CD |
> > > - CPUID_7_0_EBX_AVX512VL | CPUID_7_0_EBX_CLFLUSHOPT |
> > > - CPUID_7_0_EBX_INTEL_PT,
> > > + CPUID_7_0_EBX_AVX512VL | CPUID_7_0_EBX_CLFLUSHOPT,
> > > .features[FEAT_7_0_ECX] =
> > > CPUID_7_0_ECX_PKU | CPUID_7_0_ECX_OSPKE |
> > > CPUID_7_0_ECX_AVX512VNNI,
> > > @@ -2546,7 +2545,7 @@ static X86CPUDefinition builtin_x86_defs[]
> > > = {
> > > CPUID_7_0_EBX_HLE | CPUID_7_0_EBX_AVX2 |
> > > CPUID_7_0_EBX_SMEP |
> > > CPUID_7_0_EBX_BMI2 | CPUID_7_0_EBX_ERMS |
> > > CPUID_7_0_EBX_INVPCID |
> > > CPUID_7_0_EBX_RTM | CPUID_7_0_EBX_RDSEED |
> > > CPUID_7_0_EBX_ADX |
> > > - CPUID_7_0_EBX_SMAP | CPUID_7_0_EBX_INTEL_PT,
> > > + CPUID_7_0_EBX_SMAP,
> > > .features[FEAT_7_0_ECX] =
> > > CPUID_7_0_ECX_VBMI | CPUID_7_0_ECX_UMIP |
> > > CPUID_7_0_ECX_PKU |
> > > CPUID_7_0_ECX_OSPKE | CPUID_7_0_ECX_VBMI2 |
> > > CPUID_7_0_ECX_GFNI |
> > > @@ -2604,8 +2603,7 @@ static X86CPUDefinition builtin_x86_defs[]
> > > = {
> > > CPUID_7_0_EBX_SMAP | CPUID_7_0_EBX_CLWB |
> > > CPUID_7_0_EBX_AVX512F | CPUID_7_0_EBX_AVX512DQ |
> > > CPUID_7_0_EBX_AVX512BW | CPUID_7_0_EBX_AVX512CD |
> > > - CPUID_7_0_EBX_AVX512VL | CPUID_7_0_EBX_CLFLUSHOPT |
> > > - CPUID_7_0_EBX_INTEL_PT,
> > > + CPUID_7_0_EBX_AVX512VL | CPUID_7_0_EBX_CLFLUSHOPT,
> > > .features[FEAT_7_0_ECX] =
> > > CPUID_7_0_ECX_VBMI | CPUID_7_0_ECX_UMIP |
> > > CPUID_7_0_ECX_PKU |
> > > CPUID_7_0_ECX_OSPKE | CPUID_7_0_ECX_VBMI2 |
> > > CPUID_7_0_ECX_GFNI |
> > >
>
>
next prev parent reply other threads:[~2018-12-22 1:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 6:30 [Qemu-devel] [PATCH] i386: remove the 'INTEL_PT' CPUID bit from named CPU models Paolo Bonzini
2018-12-21 15:22 ` Philippe Mathieu-Daudé
2018-12-21 15:27 ` Paolo Bonzini
2018-12-22 1:01 ` Robert Hoo [this message]
2018-12-22 9:13 ` Paolo Bonzini
2018-12-24 4:37 ` 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=1545440514.44118.11.camel@linux.intel.com \
--to=robert.hu@linux.intel.com \
--cc=luwei.kang@intel.com \
--cc=pbonzini@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=robert.hu@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).