From: Peter Maydell <peter.maydell@linaro.org>
To: qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: patches@linaro.org, Eduardo Habkost <ehabkost@redhat.com>
Subject: [Qemu-devel] [PATCH 0/4] cpu: Implement cpu_generic_new()
Date: Mon, 13 Feb 2017 14:28:15 +0000 [thread overview]
Message-ID: <1486996099-15820-1-git-send-email-peter.maydell@linaro.org> (raw)
This patchset adds a new function cpu_generic_new()
which is similar to cpu_generic_init() except that it
does not realize the created CPU object. This means that
board code can do a "new cpu; set QOM properties; realize"
sequence without having to do all the work of splitting
the CPU model string and calling parse_features by hand.
Patch 2 clarifies a TODO comment, hopefully correctly,
based on an email conversation I had with Eduardo a
little while back.
Patches 3 and 4 change the ARM boards which currently
call parse_features by hand to use the new function.
If there's consensus that this is the right general
direction to go in, then I think that some other
architectures could also make cleanups to use this:
* cpu_s390x_create() is almost exactly this function,
give or take some fine detail of error handling
* ppc_cpu_parse_features is almost the same thing,
except that it doesn't actually create the CPU object,
it only calls parse_features
* hw/i386/pc.c does a manual parse_features
I'm not strongly attached to this particular approach
(though it seems like a reasonable one, especially given
the proliferation of different arch-specific helpers
listed above and the bugs in boards which don't call
parse_features when they should), but I would like us to
figure out and document what the right way for a board
to create and configure its CPU objects is...
Michael Davidsaver (1):
cpu: add cpu_generic_new()
Peter Maydell (3):
cpu: Clarify TODO comment in cpu_generic_new()
hw/arm/integrator: Use new cpu_generic_new()
hw/arm/virt: Use new cpu_generic_new()
include/qom/cpu.h | 17 +++++++++++++++++
hw/arm/integratorcp.c | 22 ++--------------------
hw/arm/virt.c | 24 ++----------------------
qom/cpu.c | 37 ++++++++++++++++++++++++++-----------
4 files changed, 47 insertions(+), 53 deletions(-)
--
2.7.4
next reply other threads:[~2017-02-13 14:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 14:28 Peter Maydell [this message]
2017-02-13 14:28 ` [Qemu-devel] [PATCH 1/4] cpu: add cpu_generic_new() Peter Maydell
2017-02-21 18:35 ` Eduardo Habkost
2017-02-13 14:28 ` [Qemu-devel] [PATCH 2/4] cpu: Clarify TODO comment in cpu_generic_new() Peter Maydell
2017-02-13 14:28 ` [Qemu-devel] [PATCH 3/4] hw/arm/integrator: Use new cpu_generic_new() Peter Maydell
2017-02-13 14:28 ` [Qemu-devel] [PATCH 4/4] hw/arm/virt: " Peter Maydell
2017-02-20 19:10 ` Igor Mammedov
2017-02-21 16:09 ` Eduardo Habkost
2017-02-16 16:40 ` [Qemu-devel] [Qemu-arm] [PATCH 0/4] cpu: Implement cpu_generic_new() Peter Maydell
2017-02-21 15:58 ` Eduardo Habkost
2017-02-21 17:48 ` Peter Maydell
2017-02-17 19:05 ` [Qemu-devel] " Igor Mammedov
2017-02-21 16:01 ` Eduardo Habkost
2017-06-26 13:28 ` [Qemu-devel] [Qemu-arm] " Alex Bennée
2017-06-27 2:33 ` Eduardo Habkost
2017-06-27 8:32 ` Igor Mammedov
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=1486996099-15820-1-git-send-email-peter.maydell@linaro.org \
--to=peter.maydell@linaro.org \
--cc=ehabkost@redhat.com \
--cc=patches@linaro.org \
--cc=qemu-arm@nongnu.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).