From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH 0/3] Add new CPU models
Date: Mon, 27 Feb 2012 16:33:11 -0300 [thread overview]
Message-ID: <1330371194-22315-1-git-send-email-ehabkost@redhat.com> (raw)
This series add two new CPU models to Qemu: Intel SandyBridge and AMD
Opteron_G4 (Bulldozer).
Eduardo Habkost (3):
add "tsc-deadline" flag name to feature_ecx table
add Opteron_G4 CPU model
add SandyBridge CPU model
sysconfigs/target/target-x86_64.conf | 28 ++++++++++++++++++++++++++++
target-i386/cpuid.c | 2 +-
2 files changed, 29 insertions(+), 1 deletions(-)
--
1.7.3.2
next reply other threads:[~2012-02-27 19:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-27 19:33 Eduardo Habkost [this message]
2012-02-27 19:33 ` [Qemu-devel] [PATCH 1/3] add "tsc-deadline" flag name to feature_ecx table Eduardo Habkost
2012-02-27 19:33 ` [Qemu-devel] [PATCH 2/3] add Opteron_G4 CPU model Eduardo Habkost
2012-03-06 17:17 ` Eduardo Habkost
2012-02-27 19:33 ` [Qemu-devel] [PATCH 3/3] add SandyBridge " Eduardo Habkost
2012-03-06 14:20 ` [Qemu-devel] [PATCH 0/3] Add new CPU models Eduardo Habkost
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=1330371194-22315-1-git-send-email-ehabkost@redhat.com \
--to=ehabkost@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).