qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Shannon Zhao <zhaoshenglong@huawei.com>
To: Eric Auger <eric.auger@linaro.org>,
	eric.auger@st.com, christoffer.dall@linaro.org,
	qemu-devel@nongnu.org, agraf@suse.de, pbonzini@redhat.com,
	ard.biesheuvel@linaro.org, a.rigo@virtualopensystems.com,
	joel.schopp@amd.com
Cc: peter.maydell@linaro.org, Hangaohuai <hangaohuai@huawei.com>,
	patches@linaro.org, alex.williamson@redhat.com,
	a.motakis@virtualopensystems.com, kvmarm@lists.cs.columbia.edu
Subject: Re: [Qemu-devel] [PATCH v7 0/3] machvirt dynamic sysbus device instantiation
Date: Wed, 17 Dec 2014 13:17:13 +0800	[thread overview]
Message-ID: <549111D9.5000903@huawei.com> (raw)
In-Reply-To: <1418726555-20532-1-git-send-email-eric.auger@linaro.org>

On 2014/12/16 18:42, 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.
> 
> 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 official_dynsysbus_v7
> 

Reviewed-by: Shannon Zhao <zhaoshenglong@huawei.com>

Thanks,
Shannon

      parent reply	other threads:[~2014-12-17  5:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-16 10:42 [Qemu-devel] [PATCH v7 0/3] machvirt dynamic sysbus device instantiation Eric Auger
2014-12-16 10:42 ` [Qemu-devel] [PATCH v7 1/3] hw/arm/sysbus-fdt: helpers for platform bus nodes addition Eric Auger
2014-12-16 10:42 ` [Qemu-devel] [PATCH v7 2/3] hw/arm/boot: arm_load_kernel implemented as a machine init done notifier Eric Auger
2014-12-16 10:42 ` [Qemu-devel] [PATCH v7 3/3] hw/arm/virt: add dynamic sysbus device support Eric Auger
2014-12-16 11:51 ` [Qemu-devel] [PATCH v7 0/3] machvirt dynamic sysbus device instantiation Alexander Graf
2014-12-17  5:17 ` Shannon Zhao [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=549111D9.5000903@huawei.com \
    --to=zhaoshenglong@huawei.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=a.rigo@virtualopensystems.com \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=christoffer.dall@linaro.org \
    --cc=eric.auger@linaro.org \
    --cc=eric.auger@st.com \
    --cc=hangaohuai@huawei.com \
    --cc=joel.schopp@amd.com \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=patches@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).