From: Jan Kiszka <jan.kiszka@web.de>
To: Alex Williamson <alex.williamson@redhat.com>,
David Kiarie <davidkiarie4@gmail.com>
Cc: qemu-devel@nongnu.org, mst@redhat.com, peterx@redhat.com,
valentine.sinitsyn@gmail.com, marcel@redhat.com
Subject: Re: [Qemu-devel] [V11 1/4] hw/i386: Introduce AMD IOMMU
Date: Wed, 8 Jun 2016 07:18:06 +0200 [thread overview]
Message-ID: <5757AA8E.3050306@web.de> (raw)
In-Reply-To: <20160607143650.57f316d9@ul30vt.home>
[-- Attachment #1: Type: text/plain, Size: 1567 bytes --]
On 2016-06-07 22:36, Alex Williamson wrote:
> On Sun, 22 May 2016 13:21:51 +0300
> David Kiarie <davidkiarie4@gmail.com> wrote:
>
>> Add AMD IOMMU emulaton to Qemu in addition to Intel IOMMU
>> The IOMMU does basic translation, error checking and has a
>> minimal IOTLB implementation. This IOMMU bypassed the need
>> for target aborts by responding with IOMMU_NONE access rights
>> and exempts the region 0xfee00000-0xfeefffff from translation
>> as it is the q35 interrupt region. We also advertise features
>> that are not yet implemented to please the Linux IOMMU driver.
>>
>> IOTLB aims at implementing commands on real IOMMUs which is
>> essential for debugging and may not offer any performance
>> benefits
>>
>> Signed-off-by: David Kiarie <davidkiarie4@gmail.com>
>> ---
>> hw/i386/Makefile.objs | 1 +
>> hw/i386/amd_iommu.c | 1401 +++++++++++++++++++++++++++++++++++++++++++++++++
>> hw/i386/amd_iommu.h | 340 ++++++++++++
>> include/hw/pci/pci.h | 2 +
>> 4 files changed, 1744 insertions(+)
>> create mode 100644 hw/i386/amd_iommu.c
>> create mode 100644 hw/i386/amd_iommu.h
>
> I don't see any callouts to memory_region_notify_iommu() here, so this
> won't yet support assigned devices. Do you have any plans to add that
> support? Thanks,
One after the other: correct emulation of all key features is the
primary goal, adding support for assigned devices a bonus. However, it's
not a simple one as we will probably need shadow page tables. So GSoC is
likely not long enough for this.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-06-08 5:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-22 10:21 [Qemu-devel] [V11 0/4] AMD IOMMU David Kiarie
2016-05-22 10:21 ` [Qemu-devel] [V11 1/4] hw/i386: Introduce " David Kiarie
2016-05-22 17:47 ` Jan Kiszka
2016-05-22 18:12 ` Jan Kiszka
2016-05-22 18:17 ` Jan Kiszka
2016-05-22 18:48 ` Alex Bennée
2016-05-24 12:35 ` Peter Xu
2016-05-24 13:11 ` David Kiarie
2016-06-07 20:36 ` Alex Williamson
2016-06-08 5:18 ` Jan Kiszka [this message]
2016-05-22 10:21 ` [Qemu-devel] [V11 2/4] hw/i386: ACPI IVRS table David Kiarie
2016-05-24 6:54 ` Peter Xu
2016-05-24 7:06 ` Valentine Sinitsyn
2016-06-18 8:18 ` David Kiarie
2016-06-18 12:32 ` Peter Xu
2016-06-18 12:34 ` Jan Kiszka
2016-06-20 3:36 ` Peter Xu
2016-05-22 10:21 ` [Qemu-devel] [V11 3/4] hw/core: provision for overriding emulated IOMMU David Kiarie
2016-05-24 6:51 ` Peter Xu
2016-05-24 11:49 ` Michael S. Tsirkin
2016-05-24 13:01 ` Jan Kiszka
2016-05-24 14:23 ` Marcel Apfelbaum
2016-05-22 10:21 ` [Qemu-devel] [V11 4/4] hw/pci-host: Emulate AMD IOMMU David Kiarie
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=5757AA8E.3050306@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=davidkiarie4@gmail.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=valentine.sinitsyn@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).