From: Jan Kiszka <jan.kiszka@siemens.com>
To: "Michael S. Tsirkin" <mst@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>, Le Tan <tamlokveer@gmail.com>,
Anthony Liguori <aliguori@amazon.com>,
Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH] intel_iommu: fix VTD_SID_TO_BUS
Date: Mon, 20 Oct 2014 20:27:08 +0200 [thread overview]
Message-ID: <544553FC.70204@siemens.com> (raw)
In-Reply-To: <20141020172006.GA12061@redhat.com>
On 2014-10-20 19:20, Michael S. Tsirkin wrote:
> On Mon, Oct 20, 2014 at 04:37:15PM +0200, Jan Kiszka wrote:
>> 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?
>
> PCI to PCI bridges don't work, do they?
Knut had an answer, but there was something, right.
>
>>> 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 also be fine if we flat out disallow adding virtio
> devices to such systems for now, or anything else that
> does not work.
I wouldn't (heavily used in my test setups).
> Patches for either approach aren't yet available, are they?
If no one else is quicker, I'll look into the ACPI tables.
Jan
--
Siemens AG, Corporate Technology, CT RTC ITP SES-DE
Corporate Competence Center Embedded Linux
next prev parent reply other threads:[~2014-10-20 18:27 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
2014-10-20 17:20 ` Michael S. Tsirkin
2014-10-20 18:27 ` Jan Kiszka [this message]
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=544553FC.70204@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 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).