From: "Andreas Färber" <afaerber@suse.de>
To: Eduardo Habkost <ehabkost@redhat.com>
Cc: qemu-stable <qemu-stable@nongnu.org>,
qemu-devel@nongnu.org,
"Edgar E. Iglesias" <edgar.iglesias@gmail.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Aurelien Jarno <aurelien@aurel32.net>,
Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] pc: compat: remove PCLMULQDQ from Westmere on pc-*-1.4 and older
Date: Mon, 12 Aug 2013 16:34:52 +0200 [thread overview]
Message-ID: <5208F28C.90009@suse.de> (raw)
In-Reply-To: <20130809172446.GB403@otherpad.lan.raisama.net>
Am 09.08.2013 19:24, schrieb Eduardo Habkost:
> On Fri, Aug 09, 2013 at 04:47:53PM +0200, Andreas Färber wrote:
>> Am 09.08.2013 16:11, schrieb Eduardo Habkost:
>>> commit 41cb383f42d0cb51d8e3e25e3ecebc954dd4196f made a guest-visible
>>> change by adding the PCLMULQDQ bit to Westmere without adding
>>> compatibility code to keep the ABI older machine-types. This patch fixes
>>> it by adding the missing compat code.
>>>
>>> Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
>>> ---
>>> Bug detected by the virt-test CPUID-dump comparison test case, available at:
>>> https://github.com/autotest/virt-test/pull/714
>>> ---
>>> hw/i386/pc_piix.c | 1 +
>>> hw/i386/pc_q35.c | 1 +
>>> 2 files changed, 2 insertions(+)
>>>
>>> diff --git a/hw/i386/pc_piix.c b/hw/i386/pc_piix.c
>>> index ab25458..2817092 100644
>>> --- a/hw/i386/pc_piix.c
>>> +++ b/hw/i386/pc_piix.c
>>> @@ -259,6 +259,7 @@ static void pc_init_pci_1_4(QEMUMachineInitArgs *args)
>>> {
>>> has_pvpanic = false;
>>> x86_cpu_compat_set_features("n270", FEAT_1_ECX, 0, CPUID_EXT_MOVBE);
>>> + x86_cpu_compat_set_features("Westmere", FEAT_1_ECX, 0, CPUID_EXT_PCLMULQDQ);
>>> pc_init_pci_1_5(args);
>>> }
>>>
>>> diff --git a/hw/i386/pc_q35.c b/hw/i386/pc_q35.c
>>> index 2f35d12..25c6b33 100644
>>> --- a/hw/i386/pc_q35.c
>>> +++ b/hw/i386/pc_q35.c
>>> @@ -227,6 +227,7 @@ static void pc_q35_init_1_4(QEMUMachineInitArgs *args)
>>> {
>>> has_pvpanic = false;
>>> x86_cpu_compat_set_features("n270", FEAT_1_ECX, 0, CPUID_EXT_MOVBE);
>>> + x86_cpu_compat_set_features("Westmere", FEAT_1_ECX, 0, CPUID_EXT_PCLMULQDQ);
>>> pc_q35_init_1_5(args);
>>> }
>>>
>>
>> Looks good to me, still need to test, and I should probably add
>>
>> Cc: qemu-stable@nongnu.org
>>
>> for 1.5.3 then.
>
> The patch doesn't apply cleanly on stable-1.5, but I will send a version
> for qemu-stable as well.
It's not required to apply cleanly to a specific stable- branch. :)
We need a commit id to reference in the backported version.
Thanks, applied to qom-cpu, pull coming later today.
https://github.com/afaerber/qemu-cpu/commits/qom-cpu
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-08-12 14:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 14:11 [Qemu-devel] [PATCH] pc: compat: remove PCLMULQDQ from Westmere on pc-*-1.4 and older Eduardo Habkost
2013-08-09 14:43 ` [Qemu-devel] [PATCH for-1.6] " Paolo Bonzini
2013-08-09 14:47 ` [Qemu-devel] [PATCH] " Andreas Färber
2013-08-09 17:24 ` Eduardo Habkost
2013-08-12 14:34 ` Andreas Färber [this message]
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=5208F28C.90009@suse.de \
--to=afaerber@suse.de \
--cc=aurelien@aurel32.net \
--cc=edgar.iglesias@gmail.com \
--cc=ehabkost@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@nongnu.org \
--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).