qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: "Paolo Bonzini" <pbonzini@redhat.com>,
	"John Rigby" <john.rigby@linaro.org>,
	"Andreas Färber" <afaerber@suse.de>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] New targets (was: [PATCH] qapi-schema.json: Reformat TargetType enum to one-per-line)
Date: Wed, 22 May 2013 11:10:25 -0500	[thread overview]
Message-ID: <87fvxfov0u.fsf@codemonkey.ws> (raw)
In-Reply-To: <CAFEAcA_809=OjvF=xnkuJYet8ytvXvCd+xGj9MT-o3DxB4zabw@mail.gmail.com>

Peter Maydell <peter.maydell@linaro.org> writes:

> On 22 May 2013 15:48, Anthony Liguori <aliguori@us.ibm.com> wrote:
>> Andreas Färber <afaerber@suse.de> writes:
>>> Am 22.05.2013 16:28, schrieb Anthony Liguori:
>>> So are incompletely implemented targets (wrt instruction set) eligible
>>> for upstream these days?
>>
>> Aren't most of our target incomplete by some standard?
>>
>> I thought the typical approach for a target was to get linux-user
>> working first, and then go for softmmu.  As long as linux-user can run
>> application, I think it's fair game for merging.
>>
>>> I thought they'd need to be able to run at
>>> least some small image successfully, preferably Linux where possible.
>>
>> I think that's far too high of a hurdle.
>
> I think the bar should probably be at about "either can run some
> plausible set of Linux binaries in user mode, or can run some
> softmmu image (eg linux with a minimal config", whichever the
> target submitter prefers. Basically something plausibly useful
> to somebody other than the developer.

Another way to put this, and this is true for *all* contributions, is
that the bar for acceptance is whether something is useful even if the
submitter immediately stopped contributing after the patch was merged.

Regards,

Anthony Liguori

>
> thanks
> -- PMM

  reply	other threads:[~2013-05-22 16:11 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 [this message]
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
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=87fvxfov0u.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=afaerber@suse.de \
    --cc=john.rigby@linaro.org \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.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 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).