From: Peter Xu <peterx@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Marcel Apfelbaum <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
qemu-devel@nongnu.org, yi l liu <yi.l.liu@intel.com>,
Jintack Lim <jintack@cs.columbia.edu>,
Jason Wang <jasowang@redhat.com>,
Alex Williamson <alex.williamson@redhat.com>
Subject: Re: [Qemu-devel] [PATCH v3] intel_iommu: check misordered init when realize
Date: Wed, 8 Mar 2017 16:59:17 +0800 [thread overview]
Message-ID: <20170308085917.GC7135@pxdev.xzpeter.org> (raw)
In-Reply-To: <1149211275.29885713.1488962150826.JavaMail.zimbra@redhat.com>
On Wed, Mar 08, 2017 at 03:35:50AM -0500, Paolo Bonzini wrote:
[...]
> The ordering should be explicit in the command line. Since we do not have
> cycles, it should be possible.
Current QEMU should have no restriction on parameter ordering, right?
Or do we have any existing case that:
"$QEMU -parameter1 -parameter2"
will work, while...
"$QEMU -parameter2 -parameter1"
won't work?
Thanks,
>
> The best solution would have been to add something like
>
> -device intel-iommu,id=root-complex-iommu -global mch.iommu=root-complex-iommu
>
> but it's too late for that.
-- peterx
next prev parent reply other threads:[~2017-03-08 8:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-02 3:32 [Qemu-devel] [PATCH v3] intel_iommu: check misordered init when realize Peter Xu
2017-03-02 5:13 ` Michael S. Tsirkin
2017-03-02 5:20 ` Peter Xu
2017-03-02 5:28 ` Michael S. Tsirkin
2017-03-02 6:24 ` Marcel Apfelbaum
2017-03-08 8:35 ` Paolo Bonzini
2017-03-08 8:59 ` Peter Xu [this message]
2017-03-08 9:25 ` Gerd Hoffmann
2017-03-10 7:04 ` Peter Xu
2017-03-08 10:08 ` Jason Wang
2017-03-08 13:20 ` Marcel Apfelbaum
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=20170308085917.GC7135@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=pbonzini@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.