From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "John Rigby" <john.rigby@linaro.org>,
patches@linaro.org, qemu-trivial@nongnu.org,
qemu-devel@nongnu.org, Libvirt <libvir-list@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Andreas Färber" <afaerber@suse.de>
Subject: Re: [Qemu-trivial] [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line
Date: Wed, 22 May 2013 09:29:35 -0500 [thread overview]
Message-ID: <87y5b7hyuo.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA90AJyBNtNxRa45y3zfWCj8tAq5jsqoDLmDTAZT0DK=2g@mail.gmail.com>
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?
Regards,
Anthony Liguori
>
> -- PMM
WARNING: multiple messages have this Message-ID (diff)
From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "John Rigby" <john.rigby@linaro.org>,
patches@linaro.org, qemu-trivial@nongnu.org,
qemu-devel@nongnu.org, Libvirt <libvir-list@redhat.com>,
"Paolo Bonzini" <pbonzini@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 09:29:35 -0500 [thread overview]
Message-ID: <87y5b7hyuo.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA90AJyBNtNxRa45y3zfWCj8tAq5jsqoDLmDTAZT0DK=2g@mail.gmail.com>
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?
Regards,
Anthony Liguori
>
> -- PMM
next prev parent reply other threads:[~2013-05-22 14:30 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 16:21 [Qemu-trivial] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-20 16:21 ` [Qemu-devel] " Peter Maydell
2013-05-20 16:35 ` [Qemu-trivial] " Paolo Bonzini
2013-05-20 16:35 ` [Qemu-devel] " Paolo Bonzini
2013-05-20 16:38 ` [Qemu-trivial] " Peter Maydell
2013-05-20 16:38 ` [Qemu-devel] " Peter Maydell
2013-05-20 17:14 ` [Qemu-trivial] " Paolo Bonzini
2013-05-20 17:14 ` [Qemu-devel] " Paolo Bonzini
2013-05-22 13:15 ` [Qemu-trivial] " Anthony Liguori
2013-05-22 13:15 ` Anthony Liguori
2013-05-22 13:50 ` [Qemu-trivial] " Andreas Färber
2013-05-22 13:50 ` Andreas Färber
2013-05-22 14:28 ` [Qemu-trivial] " Anthony Liguori
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-trivial] [Qemu-devel] [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line Peter Maydell
2013-05-22 13:51 ` Peter Maydell
2013-05-22 14:29 ` Anthony Liguori [this message]
2013-05-22 14:29 ` Anthony Liguori
2013-05-22 14:38 ` [Qemu-trivial] " Paolo Bonzini
2013-05-22 14:38 ` Paolo Bonzini
2013-05-24 21:38 ` [Qemu-trivial] [libvirt] " Eric Blake
2013-05-24 21:38 ` [Qemu-devel] [libvirt] " Eric Blake
2013-05-25 9:18 ` [Qemu-trivial] [libvirt] [Qemu-devel] " Peter Maydell
2013-05-25 9:18 ` [Qemu-devel] [libvirt] " Peter Maydell
2013-05-25 12:31 ` [Qemu-trivial] " Andreas Färber
2013-05-25 12:31 ` Andreas Färber
2013-05-20 16:41 ` [Qemu-trivial] [Qemu-devel] " Eric Blake
2013-05-20 16:41 ` Eric Blake
2013-05-20 16:47 ` [Qemu-trivial] " Peter Maydell
2013-05-20 16:47 ` Peter Maydell
2013-05-20 16:57 ` [Qemu-trivial] " Eric Blake
2013-05-20 16:57 ` Eric Blake
2013-05-20 17:05 ` [Qemu-trivial] " Paolo Bonzini
2013-05-20 17:05 ` [Qemu-devel] " Paolo Bonzini
2013-05-22 13:12 ` [Qemu-trivial] " Anthony Liguori
2013-05-22 13:12 ` Anthony Liguori
2013-05-22 13:38 ` [Qemu-trivial] " Peter Maydell
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=87y5b7hyuo.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=afaerber@suse.de \
--cc=john.rigby@linaro.org \
--cc=libvir-list@redhat.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--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 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.