From: "Andreas Färber" <afaerber@suse.de>
To: Josh Triplett <josh@joshtriplett.org>
Cc: Anthony Liguori <aliguori@us.ibm.com>,
qemu-devel@nongnu.org, Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [PATCH 0/3] Support configurable CPU Model-Specific Registers (MSRs) in cpudefs
Date: Sun, 15 Jan 2012 19:08:51 +0100 [thread overview]
Message-ID: <4F131633.5020604@suse.de> (raw)
In-Reply-To: <cover.1326641605.git.josh@joshtriplett.org>
Am 15.01.2012 16:39, schrieb Josh Triplett:
> Josh Triplett (3):
> Add cpudef option to GPF on unknown MSRs
> Support arbitrary additional MSRs in cpu definitions
> Handle parse failures in CPU definitions, and avoid adding a partial
> cpudef
Please prefix the subjects with "target-i386: ". PowerPC has MSRs, too.
Thanks,
Andreas
> qemu-config.c | 6 ++++
> target-i386/cpu.h | 6 ++++
> target-i386/cpuid.c | 59 ++++++++++++++++++++++++++++++++++++++++++++++-
> target-i386/op_helper.c | 36 +++++++++++++++++++++++++---
> 4 files changed, 102 insertions(+), 5 deletions(-)
--
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:[~2012-01-15 18:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 15:39 [Qemu-devel] [PATCH 0/3] Support configurable CPU Model-Specific Registers (MSRs) in cpudefs Josh Triplett
2012-01-15 15:39 ` [Qemu-devel] [PATCH 1/3] Add cpudef option to GPF on unknown MSRs Josh Triplett
2012-01-15 15:39 ` [Qemu-devel] [PATCH 2/3] Support arbitrary additional MSRs in cpu definitions Josh Triplett
2012-01-15 15:41 ` [Qemu-devel] [PATCH 3/3] Handle parse failures in CPU definitions, and avoid adding a partial cpudef Josh Triplett
2012-01-15 18:08 ` 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=4F131633.5020604@suse.de \
--to=afaerber@suse.de \
--cc=aliguori@us.ibm.com \
--cc=josh@joshtriplett.org \
--cc=paul@codesourcery.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).