From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, qemu-devel@nongnu.org
Cc: Marcel Apfelbaum <marcel.a@redhat.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: Re: [Qemu-devel] [PATCH RFC] qdev: add init order filter
Date: Thu, 9 Mar 2017 12:13:45 +0100 [thread overview]
Message-ID: <1a475607-b876-d79a-5e0b-e1a4a006c65d@redhat.com> (raw)
In-Reply-To: <1489017212-2990-1-git-send-email-mst@redhat.com>
On 09/03/2017 00:59, Michael S. Tsirkin wrote:
> Allow forcing a specific order of initialization on
> devices created with -device.
> Helpful e.g. for built-in devices such as IOMMUs which must
> exist before all other devices.
>
> Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> ---
>
> Looks like we have a ton of problems because devices
> are initialized in a random order, while we
> really want e.g. iommu to be initialized
> earlier than devices.
>
> This will be helpful for other things, e.g.
> real hardware often is initialized in a specific order,
> creating built-in devices for the board often
> has to happen in a specific order, etc.
In the specific case of PCI bus_master_as there is a simple workaround
by placing a dummy container (which lets us build the AddressSpace) and
then adding the alias region at machine_done time.
This is exactly how MemoryListener is supposed to work, so I would start
from there.
Paolo
next prev parent reply other threads:[~2017-03-09 11:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 23:59 [Qemu-devel] [PATCH RFC] qdev: add init order filter Michael S. Tsirkin
2017-03-09 11:13 ` Paolo Bonzini [this message]
2017-03-09 12:11 ` Marcel Apfelbaum
2017-03-09 12:28 ` Paolo Bonzini
2017-03-10 2:00 ` Peter Xu
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=1a475607-b876-d79a-5e0b-e1a4a006c65d@redhat.com \
--to=pbonzini@redhat.com \
--cc=marcel.a@redhat.com \
--cc=mst@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).