From: Eduardo Habkost <ehabkost@redhat.com>
To: "Kang, Luwei" <luwei.kang@intel.com>
Cc: "Strong, Beeman" <beeman.strong@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
Robert Hoo <robert.hu@linux.intel.com>,
"pbonzini@redhat.com" <pbonzini@redhat.com>,
Jiri Denemark <jdenemar@redhat.com>,
"rth@twiddle.net" <rth@twiddle.net>
Subject: Re: [PATCH v1 0/3] Remove the limitation of Intel PT CPUID info
Date: Fri, 18 Sep 2020 18:02:55 -0400 [thread overview]
Message-ID: <20200918220255.GB57321@habkost.net> (raw)
In-Reply-To: <82D7661F83C1A047AF7DC287873BF1E1738B07FF@SHSMSX104.ccr.corp.intel.com>
Hi Luwei Kang,
I was looking for info on intel-pt and just saw this series, and
it was never reviewed or merged (sorry for missing it!). Is this
still the approach we want to follow for intel-pt?
I'm CCing Jiri Denemark because this might be relevant for a
libvirt issue related to intel-pt we were investigating[1].
[1] https://bugzilla.redhat.com/show_bug.cgi?id=1853972
On Mon, Mar 30, 2020 at 09:56:09AM +0000, Kang, Luwei wrote:
> > -----Original Message-----
> > From: Kang, Luwei <luwei.kang@intel.com>
> > Sent: Tuesday, February 25, 2020 5:38 AM
> > To: pbonzini@redhat.com; rth@twiddle.net; ehabkost@redhat.com
> > Cc: qemu-devel@nongnu.org; Strong, Beeman <beeman.strong@intel.com>;
> > Kang, Luwei <luwei.kang@intel.com>
> > Subject: [PATCH v1 0/3] Remove the limitation of Intel PT CPUID info
> >
> > The Intel PT feature includes some sub-features(CPUID.(EAX=14H,ECX=0H))
> > and these sub-features are different on different HW platforms. To make the
> > live migration safety(get the same CPUID info with same cpu model on
> > different HW platform), the current Intel PT CPUID information is set to a
> > constant value(from ICELAKE Server).
> >
> > It will block the new feature in the later HW platform. what's more, the support
> > of "IP payloads" will disable the Intel PT in KVM guest(patch 1) but it will come
> > soon.
> >
> > This patchset remove this limitation and expose all the capabilities to KVM
> > guest. As it will break the live migration safe, Intel PT will be masked as
> > unmigratable.
>
> Ping.
>
> Thanks,
> Luwei Kang
>
> >
> > Luwei Kang (3):
> > i386: Remove the limitation of IP payloads for Intel PT
> > i386: Remove the CPUID limitation of Intel PT
> > i386: Mark the 'INTEL_PT' CPUID bit as unmigratable
> >
> > target/i386/cpu.c | 69 ++++---------------------------------------------------
> > 1 file changed, 5 insertions(+), 64 deletions(-)
> >
> > --
> > 1.8.3.1
>
--
Eduardo
next prev parent reply other threads:[~2020-09-18 22:04 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-24 21:38 [PATCH v1 0/3] Remove the limitation of Intel PT CPUID info Luwei Kang
2020-02-24 21:38 ` [PATCH v1 1/3] i386: Remove the limitation of IP payloads for Intel PT Luwei Kang
2020-09-25 16:15 ` Eduardo Habkost
2020-09-25 16:42 ` Strong, Beeman
2020-09-25 16:54 ` Eduardo Habkost
2020-09-25 20:23 ` Paolo Bonzini
2020-09-25 20:29 ` Eduardo Habkost
2020-09-25 20:40 ` Paolo Bonzini
2020-09-28 5:19 ` Kang, Luwei
2020-09-28 7:35 ` Paolo Bonzini
2020-09-28 12:42 ` Kang, Luwei
2020-09-28 14:12 ` Eduardo Habkost
2020-09-29 2:28 ` Kang, Luwei
2020-09-29 3:44 ` Eduardo Habkost
2020-09-28 16:46 ` Paolo Bonzini
2020-09-29 2:28 ` Kang, Luwei
2020-02-24 21:38 ` [PATCH v1 2/3] i386: Remove the CPUID limitation of " Luwei Kang
2020-02-24 21:38 ` [PATCH v1 3/3] i386: Mark the 'INTEL_PT' CPUID bit as unmigratable Luwei Kang
2020-03-30 9:56 ` [PATCH v1 0/3] Remove the limitation of Intel PT CPUID info Kang, Luwei
2020-09-18 22:02 ` Eduardo Habkost [this message]
2020-09-21 7:49 ` Kang, Luwei
2020-09-21 16:50 ` Eduardo Habkost
2020-09-23 2:52 ` Kang, Luwei
2020-09-23 14:15 ` Eduardo Habkost
2020-09-24 12:47 ` Kang, Luwei
2020-09-24 13:34 ` Eduardo Habkost
2020-09-25 8:20 ` Kang, Luwei
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=20200918220255.GB57321@habkost.net \
--to=ehabkost@redhat.com \
--cc=beeman.strong@intel.com \
--cc=jdenemar@redhat.com \
--cc=luwei.kang@intel.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=robert.hu@linux.intel.com \
--cc=rth@twiddle.net \
/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).