qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: Markus Armbruster <armbru@redhat.com>,
	Marcel Apfelbaum <marcel@redhat.com>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 0/3] qdev: order devices by priority before creating them
Date: Wed, 11 May 2016 17:09:56 +0200	[thread overview]
Message-ID: <57334B44.6070709@redhat.com> (raw)
In-Reply-To: <20160511165429-mutt-send-email-mst@redhat.com>



On 11/05/2016 15:55, Michael S. Tsirkin wrote:
> > Could they "know" it by adding an iommu=foo argument to e.g. the PCI
> > bridge, pointing to the IOMMU device?
> 
> People don't create the pci host bridge though, it's
> part of the default machine.

If there's just one of its class you can use -global (similar to how we
use it for floppies).

Thanks,

Paolo

  reply	other threads:[~2016-05-11 15:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 17:47 [Qemu-devel] [PATCH RFC 0/3] qdev: order devices by priority before creating them Marcel Apfelbaum
2016-05-09 17:47 ` [Qemu-devel] [PATCH RFC 1/3] qdev: add device creation priority flag Marcel Apfelbaum
2016-05-09 17:47 ` [Qemu-devel] [PATCH RFC 2/3] vl.c: create devices by their " Marcel Apfelbaum
2016-05-09 17:47 ` [Qemu-devel] [PATCH RFC 3/3] hw/pci-bridge: add the corresponding " Marcel Apfelbaum
2016-05-10  8:28 ` [Qemu-devel] [PATCH RFC 0/3] qdev: order devices by priority before creating them Markus Armbruster
2016-05-10 11:05   ` Marcel Apfelbaum
2016-05-11  7:51     ` Markus Armbruster
2016-05-15 11:23       ` Marcel Apfelbaum
2016-05-10 15:36   ` Michael S. Tsirkin
2016-05-10 17:13     ` Paolo Bonzini
2016-05-11 13:55       ` Michael S. Tsirkin
2016-05-11 15:09         ` Paolo Bonzini [this message]
2016-05-11 15:19           ` Michael S. Tsirkin
2016-05-11 15:25             ` Paolo Bonzini

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=57334B44.6070709@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=armbru@redhat.com \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --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).