From: Alexander Graf <agraf@suse.de>
To: Eric Auger <eric.auger@linaro.org>,
eric.auger@st.com, christoffer.dall@linaro.org,
qemu-devel@nongnu.org, pbonzini@redhat.com,
kim.phillips@freescale.com, a.rigo@virtualopensystems.com,
manish.jaggi@caviumnetworks.com, joel.schopp@amd.com
Cc: peter.maydell@linaro.org, patches@linaro.org,
will.deacon@arm.com, stuart.yoder@freescale.com,
Bharat.Bhushan@freescale.com, alex.williamson@redhat.com,
a.motakis@virtualopensystems.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH v4 0/6] machvirt dynamic sysbus device instantiation
Date: Wed, 05 Nov 2014 11:21:25 +0100 [thread overview]
Message-ID: <5459FA25.7000603@suse.de> (raw)
In-Reply-To: <1414763612-4939-1-git-send-email-eric.auger@linaro.org>
On 31.10.14 14:53, Eric Auger wrote:
> This patch series enables machvirt to dynamically instantiate sysbus
> devices from command line (using -device option).
>
> All those sysbus devices are plugged onto a platform bus. This latter
> device is instantiated in machvirt and takes care of the binding of
> children sysbus devices on a machine init done notifier. The device
> tree node generation for children dynamic sysbus device also happens
> on a subsequent notifier that must be executed after the above one.
> machvirt registers that notifier before the platform bus creation to
> make sure notifiers are executed in the right order: dt generation
> after actual QOM binding.
>
> Very few sysbus devices are supposed to be instantiated that way.
> VFIO devices belong to them.
>
> Node creation really is architecture specific. On ARM the dynamic
> sysbus device node creation is implemented in a new C module,
> hw/arm/sysbus-fdt.c and not in the machine file.
>
> This series applies on top of Alex Graf's series
> [PATCH v3 0/7] Dynamic sysbus device allocation support
> http://lists.nongnu.org/archive/html/qemu-devel/2014-09/msg04860.html
>
> Machvirt transformations and sysbus-fdt are largely inspired from Alex work.
>
> The patch series can be found at:
> http://git.linaro.org/people/eric.auger/qemu.git (branch vfio_integ_v7)
Overall the approach looks sane to me. I'm not 100% convinced it's a
good idea to make the fdt generation "arm generic", but I'll leave that
for Peter to decide. On PPC this definitely wouldn't fly with all the
different subarchs. I'm not sure whether ARM is more standardized on the
device tree generation, especially with different #address-size
properties and the likes.
Alex
prev parent reply other threads:[~2014-11-05 10:21 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 13:53 [Qemu-devel] [PATCH v4 0/6] machvirt dynamic sysbus device instantiation Eric Auger
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 1/6] hw/arm/boot: load_dtb becomes non static arm_load_dtb Eric Auger
2014-11-27 9:00 ` Shannon Zhao
2014-11-27 9:19 ` Eric Auger
2014-11-27 10:17 ` Shannon Zhao
2014-11-27 10:29 ` Eric Auger
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 2/6] hw/arm/boot: dtb start and limit moved in arm_boot_info Eric Auger
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 3/6] hw/arm/boot: do not free VirtBoardInfo fdt in arm_load_dtb Eric Auger
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 4/6] hw/arm: add a new modify_dtb_opaque field in arm_boot_info Eric Auger
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 5/6] hw/arm/sysbus-fdt: helpers for platform bus nodes addition Eric Auger
2014-11-05 10:19 ` Alexander Graf
2014-11-27 12:07 ` Shannon Zhao
2014-11-27 12:25 ` Eric Auger
2014-11-27 12:56 ` Shannon Zhao
2014-11-27 13:14 ` Alexander Graf
2014-11-27 13:16 ` Eric Auger
2014-11-27 13:36 ` Shannon Zhao
2014-10-31 13:53 ` [Qemu-devel] [PATCH v4 6/6] hw/arm/virt: add dynamic sysbus device support Eric Auger
2014-11-05 10:19 ` Alexander Graf
2014-11-05 10:21 ` Alexander Graf [this message]
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=5459FA25.7000603@suse.de \
--to=agraf@suse.de \
--cc=Bharat.Bhushan@freescale.com \
--cc=a.motakis@virtualopensystems.com \
--cc=a.rigo@virtualopensystems.com \
--cc=alex.williamson@redhat.com \
--cc=christoffer.dall@linaro.org \
--cc=eric.auger@linaro.org \
--cc=eric.auger@st.com \
--cc=joel.schopp@amd.com \
--cc=kim.phillips@freescale.com \
--cc=kvmarm@lists.cs.columbia.edu \
--cc=manish.jaggi@caviumnetworks.com \
--cc=patches@linaro.org \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=stuart.yoder@freescale.com \
--cc=will.deacon@arm.com \
/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).