From: john cooper <john.cooper@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: KVM list <kvm@vger.kernel.org>,
qemu-devel@nongnu.org, "Przywara, Andre" <Andre.Przywara@amd.com>,
john.cooper@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Add cpu model configuration support.. (resend)
Date: Sun, 14 Feb 2010 01:52:08 -0500 [thread overview]
Message-ID: <4B779D98.3070300@redhat.com> (raw)
In-Reply-To: <4B731049.4050707@linux.vnet.ibm.com>
Anthony Liguori wrote:
> On 02/01/2010 01:02 PM, john cooper wrote:
>> [target-x86_64.conf was unintentionally omitted from the earlier patch]
>>
>> This is a reimplementation of prior versions which adds
>> the ability to define cpu models for contemporary processors.
>> The added models are likewise selected via -cpu<name>,
>> and are intended to displace the existing convention
>> of "-cpu qemu64" augmented with a series of feature flags
>>
>
> This breaks the arm-softmmu build.
Ugh, does indeed as well as a few other builds.
Updated patch follows.
-john
--
john.cooper@redhat.com
WARNING: multiple messages have this Message-ID (diff)
From: john cooper <john.cooper@redhat.com>
To: Anthony Liguori <aliguori@linux.vnet.ibm.com>
Cc: john.cooper@redhat.com, "Przywara,
Andre" <Andre.Przywara@amd.com>,
qemu-devel@nongnu.org, KVM list <kvm@vger.kernel.org>
Subject: Re: [Qemu-devel] [PATCH] Add cpu model configuration support.. (resend)
Date: Sun, 14 Feb 2010 01:52:08 -0500 [thread overview]
Message-ID: <4B779D98.3070300@redhat.com> (raw)
In-Reply-To: <4B731049.4050707@linux.vnet.ibm.com>
Anthony Liguori wrote:
> On 02/01/2010 01:02 PM, john cooper wrote:
>> [target-x86_64.conf was unintentionally omitted from the earlier patch]
>>
>> This is a reimplementation of prior versions which adds
>> the ability to define cpu models for contemporary processors.
>> The added models are likewise selected via -cpu<name>,
>> and are intended to displace the existing convention
>> of "-cpu qemu64" augmented with a series of feature flags
>>
>
> This breaks the arm-softmmu build.
Ugh, does indeed as well as a few other builds.
Updated patch follows.
-john
--
john.cooper@redhat.com
next prev parent reply other threads:[~2010-02-14 7:02 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-01 19:02 [PATCH] Add cpu model configuration support.. (resend) john cooper
2010-02-01 19:02 ` [Qemu-devel] " john cooper
2010-02-02 10:17 ` Andre Przywara
2010-02-02 10:17 ` [Qemu-devel] " Andre Przywara
2010-02-02 11:07 ` Andre Przywara
2010-02-02 11:07 ` [Qemu-devel] " Andre Przywara
2010-02-02 19:34 ` john cooper
2010-02-02 19:34 ` [Qemu-devel] " john cooper
2010-02-06 18:59 ` [PATCH] Add assignment operation to config file parser john cooper
2010-02-06 18:59 ` [Qemu-devel] " john cooper
2010-02-07 16:24 ` Anthony Liguori
2010-02-07 16:24 ` Anthony Liguori
2010-02-08 13:21 ` Gerd Hoffmann
2010-02-08 16:00 ` john cooper
2010-02-08 16:00 ` john cooper
2010-06-09 8:05 ` [Qemu-devel] [PATCH] Add optional dump of default config file paths john cooper
2010-06-14 17:01 ` Anthony Liguori
2010-06-14 17:07 ` Daniel P. Berrange
2010-06-14 17:59 ` john cooper
2010-06-14 19:13 ` Anthony Liguori
2010-02-10 20:00 ` [Qemu-devel] [PATCH] Add cpu model configuration support.. (resend) Anthony Liguori
2010-02-10 20:00 ` Anthony Liguori
2010-02-14 6:52 ` john cooper [this message]
2010-02-14 6:52 ` john cooper
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=4B779D98.3070300@redhat.com \
--to=john.cooper@redhat.com \
--cc=Andre.Przywara@amd.com \
--cc=aliguori@linux.vnet.ibm.com \
--cc=kvm@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.