All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Xu <peterx@redhat.com>
To: Marcel Apfelbaum <marcel@redhat.com>
Cc: Jason Wang <jasowang@redhat.com>,
	"Michael S. Tsirkin" <mst@redhat.com>,
	Alex Williamson <alex.williamson@redhat.com>,
	yi.l.liu@intel.com, qemu-devel@nongnu.org,
	Jintack Lim <jintack@cs.columbia.edu>
Subject: Re: [Qemu-devel] [PATCH v2] intel_iommu: check misordered init when realize
Date: Wed, 1 Mar 2017 17:18:31 +0800	[thread overview]
Message-ID: <20170301091831.GF13926@pxdev.xzpeter.org> (raw)
In-Reply-To: <a35dbe8f-770e-c792-e5ea-1f4f8ef8df37@redhat.com>

On Wed, Mar 01, 2017 at 09:03:47AM +0200, Marcel Apfelbaum wrote:
> On 03/01/2017 06:14 AM, Jason Wang wrote:

[...]

> Hi Jason,
> 
> I am not saying we don't need to create the IOMMU before some other device,
> I just don't think that the command line order should matter to user.
> 
> BTW, are you working on a way to limit the IOMMU scope to a specific set of devices?
> If yes, this approach will also help you work.

Marcel,

Do you have any plan after 2.9 to re-arrange the init order thing a
bit? In general, maybe we need an ordering support for devices.
Besides that, I am thinking whether it would be wise that we just init
the IOMMUs during machine init just like before, but keep the
"-device" interface? After all, at least the root IOMMU device should
be with root complex, and it feels a little strange we just split the
init process apart (we delay the IOMMU init into device
initializations).

Not sure whether above makes sense though. Thanks,

-- peterx

  parent reply	other threads:[~2017-03-01  9:18 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-24  4:29 [Qemu-devel] [PATCH v2] intel_iommu: check misordered init when realize Peter Xu
2017-02-24  5:07 ` Pankaj Gupta
2017-02-24  5:50   ` Peter Xu
2017-02-24  6:35     ` Pankaj Gupta
2017-02-24  7:10       ` Peter Xu
2017-02-24  8:42         ` Pankaj Gupta
2017-02-28 14:42 ` Marcel Apfelbaum
2017-03-01  2:36   ` Peter Xu
2017-03-01  3:23     ` Michael S. Tsirkin
2017-03-01  4:14       ` Jason Wang
2017-03-01  7:03         ` Marcel Apfelbaum
2017-03-01  8:43           ` Jason Wang
2017-03-01  9:05             ` Marcel Apfelbaum
2017-03-01  9:18           ` Peter Xu [this message]
2017-03-01  9:29             ` Marcel Apfelbaum
2017-03-01  9:59               ` Peter Xu
2017-03-01 12:32                 ` Marcel Apfelbaum
2017-03-02  3:45                   ` Peter Xu
2017-03-02  3:39         ` 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=20170301091831.GF13926@pxdev.xzpeter.org \
    --to=peterx@redhat.com \
    --cc=alex.williamson@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=jintack@cs.columbia.edu \
    --cc=marcel@redhat.com \
    --cc=mst@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=yi.l.liu@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.