From: "J. Mayer" <l_indien@magic.fr>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] RFC: avoid #ifdef for target cpu list - for x86, too.
Date: Sat, 13 Oct 2007 11:56:27 +0200 [thread overview]
Message-ID: <1192269387.9976.307.camel@rapid> (raw)
In-Reply-To: <20071012085431.GA13221@karma.qumranet.com>
On Fri, 2007-10-12 at 10:54 +0200, Dan Kenigsberg wrote:
> This seems like a good excuse to send my suggested -cpu option for the
> x86 target. It is just like my previous "take 4", but fits to the newly
> unified cpu_list.
I don't know x86 so well to comment the x86 CPU definitions, but having
this option for x86 too is welcome...
[...]
--
J. Mayer <l_indien@magic.fr>
Never organized
next prev parent reply other threads:[~2007-10-13 9:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-11 22:28 [Fwd: [Qemu-devel] RFC: avoid #ifdef for target cpu list] J. Mayer
2007-10-12 8:54 ` [Qemu-devel] RFC: avoid #ifdef for target cpu list - for x86, too Dan Kenigsberg
2007-10-13 9:56 ` J. Mayer [this message]
2007-10-22 0:47 ` Thiemo Seufer
2007-10-22 8:45 ` Dan Kenigsberg
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=1192269387.9976.307.camel@rapid \
--to=l_indien@magic.fr \
--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).