From: Eduardo Habkost <ehabkost@redhat.com>
To: "Philippe Mathieu-Daudé" <f4bug@amsat.org>
Cc: Igor Mammedov <imammedo@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-devel@nongnu.org,
Alistair Francis <alistair.francis@xilinx.com>,
marcel@redhat.com
Subject: Re: [Qemu-devel] [RFC v1 0/2] Add a valid_cpu_types property
Date: Tue, 19 Sep 2017 07:42:59 -0300 [thread overview]
Message-ID: <20170919104259.GB3030@localhost.localdomain> (raw)
In-Reply-To: <36b5e019-4f30-666b-7479-df8de0a6f936@amsat.org>
On Tue, Sep 19, 2017 at 06:51:23AM -0300, Philippe Mathieu-Daudé wrote:
> On 09/18/2017 07:55 PM, Eduardo Habkost wrote:
> > On Mon, Sep 18, 2017 at 06:57:19PM -0300, Philippe Mathieu-Daudé wrote:
> > > add a property to restrict the CPU for SoCs once on machine creation and avoid
> > > duplicate code in each board.
> > >
> > > Signed-off-by: Philippe Mathieu-Daudé <f4bug@amsat.org>
> >
> > The valid_cpu_types approach implemented by Alistair is more
> > generic:
> > Subject: [Qemu-devel] [RFC v1 0/2] Add a valid_cpu_types property
> > Message-ID: <cover.1504656490.git.alistair.francis@xilinx.com>
> >
> > With it, boards that don't support other CPUs just need to set
> > valid_cpu_types = { default_cpu_type }.
>
> Oh thank for pointing this out, I missed his series.
>
> Many people waiting for Igor series to land ;)
I plan to queue it today, and get a pull request out today or
tomorrow.
--
Eduardo
next prev parent reply other threads:[~2017-09-19 10:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-18 21:57 [Qemu-devel] [RFC PATCH] vl.c: add is_system_on_chip flag to force board default cpu Philippe Mathieu-Daudé
2017-09-18 22:55 ` [Qemu-devel] [RFC v1 0/2] Add a valid_cpu_types property Eduardo Habkost
2017-09-19 9:51 ` Philippe Mathieu-Daudé
2017-09-19 10:42 ` Eduardo Habkost [this message]
2017-09-19 9:03 ` [Qemu-devel] [RFC PATCH] vl.c: add is_system_on_chip flag to force board default cpu Peter Maydell
2017-09-19 18:16 ` Alistair Francis
-- strict thread matches above, loose matches on Subject: below --
2017-09-06 0:11 [Qemu-devel] [RFC v1 0/2] Add a valid_cpu_types property Alistair Francis
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=20170919104259.GB3030@localhost.localdomain \
--to=ehabkost@redhat.com \
--cc=alistair.francis@xilinx.com \
--cc=f4bug@amsat.org \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--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).