From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>, Le Tan <tamlokveer@gmail.com>
Cc: Markus Armbruster <armbru@redhat.com>,
Anthony Liguori <aliguori@amazon.com>,
qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: fix VTD_SID_TO_BUS
Date: Mon, 20 Oct 2014 16:37:15 +0200 [thread overview]
Message-ID: <54451E1B.9080801@siemens.com> (raw)
In-Reply-To: <20141020142356.GD11062@redhat.com>
On 2014-10-20 16:23, Michael S. Tsirkin wrote:
>
> WRT intel_iommu, it does not yet seem to be as fully functional as I
> hoped.
What is missing or broken?
> People also discussed the best way to handle virtio versus iommu
> (it bypasses it ATM).
We need to declare in the ACPI tables that the emulated IOMMUs do not
cover those "special" virtio devices.
> I'd like to suggest we hide the iommu from the command line
> help for 2.2, this way people don't activate it mistakenly.
>
> Let's make it more complete and then enable for 2.3.
>
> Thoughts?
We need the list of issues on the table, then we can decide.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-10-20 14:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-20 9:40 [Qemu-devel] [PATCH] intel_iommu: fix VTD_SID_TO_BUS Michael S. Tsirkin
2014-10-20 11:41 ` Markus Armbruster
2014-10-20 12:14 ` Le Tan
2014-10-20 14:23 ` Michael S. Tsirkin
2014-10-20 14:37 ` Jan Kiszka [this message]
2014-10-20 17:20 ` Michael S. Tsirkin
2014-10-20 18:27 ` Jan Kiszka
2014-10-20 15:15 ` Knut Omang
2014-10-20 18:18 ` Jan Kiszka
2014-10-20 19:03 ` Knut Omang
2014-10-20 19:37 ` Knut Omang
2014-10-20 22:53 ` Knut Omang
2014-10-20 14:48 ` Knut Omang
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=54451E1B.9080801@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=aliguori@amazon.com \
--cc=armbru@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=tamlokveer@gmail.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.