From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org, "Andreas Färber" <afaerber@suse.de>
Cc: Igor Mammedov <imammedo@redhat.com>, Gleb Natapov <gleb@redhat.com>
Subject: [Qemu-devel] [PATCH qom-cpu 0/3] Conroe/Penryn/Nehalem CPUID family/level fixes
Date: Mon, 27 May 2013 17:23:52 -0300 [thread overview]
Message-ID: <1369686235-11090-1-git-send-email-ehabkost@redhat.com> (raw)
This series changes the CPUID family and level fields of the Conroe, Penryn, and
Nehalem CPU models.
Testing: those model/level values have been in use on Red Hat
Enterprise Linux since version 6.0 (released in 2010). The fix wasn't
submitted to QEMU earlier because we didn't have a good mechanism and
clear procedure to update CPUID values of existing CPU models in QEMU.
Eduardo Habkost (3):
pc: create pc-*-1.6 machine-types
target-i386: update model values on Conroe/Penryn/Nehalem CPU models
target-i386: set level=4 on Conroe/Penryn/Nehalem
hw/i386/pc_piix.c | 18 ++++++++++++++++--
hw/i386/pc_q35.c | 16 +++++++++++++++-
include/hw/i386/pc.h | 28 ++++++++++++++++++++++++++++
target-i386/cpu.c | 12 ++++++------
4 files changed, 65 insertions(+), 9 deletions(-)
--
1.8.1.4
next reply other threads:[~2013-05-27 20:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-27 20:23 Eduardo Habkost [this message]
2013-05-27 20:23 ` [Qemu-devel] [PATCH qom-cpu 1/3] pc: create pc-*-1.6 machine-types Eduardo Habkost
2013-05-27 20:23 ` [Qemu-devel] [PATCH qom-cpu 2/3] target-i386: update model values on Conroe/Penryn/Nehalem CPU models Eduardo Habkost
2013-05-27 20:23 ` [Qemu-devel] [PATCH qom-cpu 3/3] target-i386: set level=4 on Conroe/Penryn/Nehalem Eduardo Habkost
2013-05-27 20:30 ` [Qemu-devel] [PATCH qom-cpu 0/3] Conroe/Penryn/Nehalem CPUID family/level fixes Andreas Färber
2013-05-28 9:31 ` Igor Mammedov
2013-05-30 16:17 ` Andreas Färber
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=1369686235-11090-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=afaerber@suse.de \
--cc=gleb@redhat.com \
--cc=imammedo@redhat.com \
--cc=qemu-devel@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).