qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
	"John Rigby" <john.rigby@linaro.org>,
	patches@linaro.org, qemu-trivial@nongnu.org,
	qemu-devel@nongnu.org, Libvirt <libvir-list@redhat.com>,
	"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line
Date: Wed, 22 May 2013 16:38:27 +0200	[thread overview]
Message-ID: <519CD863.3080205@redhat.com> (raw)
In-Reply-To: <87y5b7hyuo.fsf@codemonkey.ws>

Il 22/05/2013 16:29, Anthony Liguori ha scritto:
> Peter Maydell <peter.maydell@linaro.org> writes:
> 
>> On 22 May 2013 14:15, Anthony Liguori <aliguori@us.ibm.com> wrote:
>>> Paolo Bonzini <pbonzini@redhat.com> writes:
>>>> You
>>>> don't need to know what targets were supported in the version that you
>>>> compiled from.  Only one target is supported in this executable
>>>> anyway.
>>>
>>> It seems useful to me.  One day we may support multiple targets per
>>> executable.
>>
>> Why would you care about which architectures the executable supports?
>> What you actually want to know is which machine models are supported;
>> whether board foo happens to be ARM or PPC isn't really very interesting
>> IMHO.
> 
> That's a very good point.  It was the libvirt folks that requested
> this.  Perhaps they can shed some light on the logic?

There is processor-dependent logic in libvirt, for example the CPUID bits.

Paolo

  reply	other threads:[~2013-05-22 14:38 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-20 16:21 [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-20 16:35 ` Paolo Bonzini
2013-05-20 16:38   ` Peter Maydell
2013-05-20 17:14     ` Paolo Bonzini
2013-05-22 13:15   ` Anthony Liguori
2013-05-22 13:50     ` Andreas Färber
2013-05-22 14:28       ` Anthony Liguori
2013-05-22 14:34         ` [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line) Andreas Färber
2013-05-22 14:48           ` Anthony Liguori
2013-05-22 15:33             ` Peter Maydell
2013-05-22 16:10               ` Anthony Liguori
2013-05-22 13:51     ` [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-22 14:29       ` Anthony Liguori
2013-05-22 14:38         ` Paolo Bonzini [this message]
2013-05-24 21:38         ` [Qemu-devel] [libvirt] " Eric Blake
2013-05-25  9:18           ` Peter Maydell
2013-05-25 12:31             ` Andreas Färber
2013-05-20 16:41 ` [Qemu-devel] " Eric Blake
2013-05-20 16:47   ` Peter Maydell
2013-05-20 16:57     ` Eric Blake
2013-05-20 17:05       ` Paolo Bonzini
2013-05-22 13:12 ` Anthony Liguori
2013-05-22 13:38   ` Peter Maydell

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=519CD863.3080205@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=afaerber@suse.de \
    --cc=aliguori@us.ibm.com \
    --cc=john.rigby@linaro.org \
    --cc=libvir-list@redhat.com \
    --cc=patches@linaro.org \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).