From: Paolo Bonzini <pbonzini@redhat.com>
To: "Robert Hoo" <robert.hu@linux.intel.com>,
"Daniel P. Berrangé" <berrange@redhat.com>,
kai.huang@intel.com, luwei.kang@intel.com
Cc: robert.hu@intel.com, thomas.lendacky@amd.com,
ehabkost@redhat.com, qemu-devel@nongnu.org, 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 16:03:55 +0100 [thread overview]
Message-ID: <bd0addb6-9d5f-b4dc-8cd9-f2d096ccd16c@redhat.com> (raw)
In-Reply-To: <1545401072.44118.7.camel@linux.intel.com>
On 21/12/18 15:04, Robert Hoo wrote:
>> 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.
>
> My apologies for carelessness.
No problem. In the future please check that "-cpu Icelake-Client"
doesn't have warnings such as
qemu-system-x86_64: warning: host doesn't support requested feature:
CPUID.07H:EBX.intel-pt [bit 25]
when run on an Icelake-Client host.
> I've seen you patch for INTEL_PT. So am I going to resend these 2
> patches and Cc qemu-stable? or simply reply these 2 patches adding
> qemu-stable in Cc list?
I can take care of that, thanks.
Paolo
next prev parent reply other threads:[~2018-12-21 15:04 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
2018-12-21 14:04 ` Robert Hoo
2018-12-21 15:03 ` Paolo Bonzini [this message]
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=bd0addb6-9d5f-b4dc-8cd9-f2d096ccd16c@redhat.com \
--to=pbonzini@redhat.com \
--cc=berrange@redhat.com \
--cc=ehabkost@redhat.com \
--cc=kai.huang@intel.com \
--cc=luwei.kang@intel.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).