All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: Stefan Weil <sw@weilnetz.de>,
	QEMU Developers <qemu-devel@nongnu.org>,
	Alexander Graf <agraf@suse.de>,
	Paolo Bonzini <pbonzini@redhat.com>,
	Laszlo Ersek <lersek@redhat.com>,
	Richard Henderson <rth@twiddle.net>
Subject: Re: [Qemu-devel] [PATCH] target-arm: fix build on fedora
Date: Mon, 23 Dec 2013 16:15:48 +0200	[thread overview]
Message-ID: <20131223141548.GC21800@redhat.com> (raw)
In-Reply-To: <CAFEAcA8EP8pEpATR0kvbOJRL8HwCk8DfS6LtNrN-X60xGXw0iw@mail.gmail.com>

On Mon, Dec 23, 2013 at 01:41:50PM +0000, Peter Maydell wrote:
> On 23 December 2013 13:32, Stefan Weil <sw@weilnetz.de> wrote:
> > Am 23.12.2013 13:59, schrieb Peter Maydell:
> >> On 23 December 2013 12:50, Paolo Bonzini <pbonzini@redhat.com> wrote:
> >>> Il 23/12/2013 13:37, Peter Maydell ha scritto:
> >>>> At a minimum, if we take this approach we should add TODO comments
> >>>> to the effect that the NULL terminator and the if() can be removed
> >>>> when the first real AArch64 CPU is added.
> >>>>
> >>>> I think I'd rather put the if (!info->name) continue into the function
> >>>> which is doing the looping over the array.
> >>> Or just change the termination condition from a check on the array size
> >>> to one on info->name.
> >> That would take it out of line with the equivalent 32 bit ARM code
> >> (and also moxie and openrisc for what little that's worth) and be
> >> fractionally more tedious to revert later.
> 
> > What about adding a dummy CPU (which can be removed later)?
> 
> That would be user-visible, which seems a bad thing.
> I agree that there aren't any fantastic solutions here;
> I think something more or less like Michael's patch with
> a TODO note so it's easy for me to take it out again when
> I add an actual A57 emulation in a couple of months will
> do. This is just a temporary thing since at the moment we
> only support -cpu any for userspace and -cpu host for KVM.
> 
> thanks
> -- PMM

OK, ack my patch then? I'll add a comment
/* TODO: remove when we support more CPUs. */

  reply	other threads:[~2013-12-23 14:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-23 11:56 [Qemu-devel] [PATCH] target-arm: fix build on fedora Michael S. Tsirkin
2013-12-23 12:37 ` Peter Maydell
2013-12-23 12:50   ` Paolo Bonzini
2013-12-23 12:59     ` Peter Maydell
2013-12-23 13:32       ` Stefan Weil
2013-12-23 13:41         ` Peter Maydell
2013-12-23 14:15           ` Michael S. Tsirkin [this message]
2013-12-23 14:15             ` Peter Maydell
2013-12-23 13:45   ` Andreas Färber
2013-12-23 13:56     ` Peter Maydell
2013-12-23 14:16   ` Michael S. Tsirkin

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=20131223141548.GC21800@redhat.com \
    --to=mst@redhat.com \
    --cc=agraf@suse.de \
    --cc=lersek@redhat.com \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rth@twiddle.net \
    --cc=sw@weilnetz.de \
    /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.