From: Paolo Bonzini <pbonzini@redhat.com>
To: "Kang, Luwei" <luwei.kang@intel.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: "ehabkost@redhat.com" <ehabkost@redhat.com>,
"qemu-stable@nongnu.org" <qemu-stable@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] i386: mark the 'INTEL_PT' CPUID bit as unmigratable
Date: Fri, 28 Dec 2018 14:53:22 +0100 [thread overview]
Message-ID: <ed344ef0-c519-1c71-c0ad-fb523a5dc516@redhat.com> (raw)
In-Reply-To: <82D7661F83C1A047AF7DC287873BF1E172C97D77@SHSMSX101.ccr.corp.intel.com>
On 25/12/18 09:23, Kang, Luwei wrote:
>> From: Qemu-devel [mailto:qemu-devel-bounces+luwei.kang=intel.com@nongnu.org] On Behalf Of Paolo Bonzini
>> Sent: Friday, December 21, 2018 8:44 PM
>> To: qemu-devel@nongnu.org
>> Cc: ehabkost@redhat.com; qemu-stable@nongnu.org
>> Subject: [Qemu-devel] [PATCH] i386: mark the 'INTEL_PT' CPUID bit as unmigratable
>>
>> Marshaling of processor tracing MSRs is not yet implemented in QEMU, mark the feature as unmigratable.
>
> Hi Paolo,
> I think Intel PT has supported live migration. I don't understand what you mean.
>
> commit b77146e9a129bcdb60edc23639211679ae846a92
> Author: Chao Peng <chao.p.peng@linux.intel.com>
> Date: Mon Mar 5 00:48:36 2018 +0800
> i386: Add support to get/set/migrate Intel Processor Trace feature
Indeed. I had forgotten this patch because it was committed so long
before the kernel parts (which really should not happen, but Eduardo and
I miscommunicated on it). Can you check that it still works?
Paolo
next prev parent reply other threads:[~2018-12-28 14:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-21 12:44 [Qemu-devel] [PATCH] i386: mark the 'INTEL_PT' CPUID bit as unmigratable Paolo Bonzini
2018-12-25 8:23 ` Kang, Luwei
2018-12-28 13:53 ` Paolo Bonzini [this message]
2018-12-29 1:28 ` Eduardo Habkost
2019-01-02 1:30 ` Kang, Luwei
2019-01-05 2:35 ` Eduardo Habkost
2019-01-02 1:06 ` Kang, Luwei
2018-12-26 8:24 ` no-reply
2018-12-26 8:26 ` no-reply
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=ed344ef0-c519-1c71-c0ad-fb523a5dc516@redhat.com \
--to=pbonzini@redhat.com \
--cc=ehabkost@redhat.com \
--cc=luwei.kang@intel.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
/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).