From: Jan Kiszka <jan.kiszka@web.de>
To: David Kiarie <davidkiarie4@gmail.com>,
Eduardo Habkost <ehabkost@redhat.com>
Cc: QEMU Developers <qemu-devel@nongnu.org>,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Peter Xu <peterx@redhat.com>,
alex.williamson@redhat.com,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
Subject: Re: [Qemu-devel] [V12 0/4] AMD IOMMU
Date: Wed, 15 Jun 2016 19:13:37 +0200 [thread overview]
Message-ID: <57618CC1.9000505@web.de> (raw)
In-Reply-To: <CABdVeABJd=P_tZ5gL9zaps2NC1WgYztvoKRTw0eMcWYAH_RcXA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1849 bytes --]
On 2016-06-15 19:07, David Kiarie wrote:
> On Wed, Jun 15, 2016 at 5:26 PM, Eduardo Habkost <ehabkost@redhat.com> wrote:
>> On Wed, Jun 15, 2016 at 03:21:48PM +0300, David Kiarie wrote:
>>> Hi all,
>>>
>>> This patchset adds basic AMD IOMMU emulation support to Qemu.
>>>
>>> Changes since V11
>>> -AMD IOMMU is not started with -device amd-iommu (with a dependency on Marcel's patches).
>>> -IOMMU commands are represented using bitfields which is less error prone and more readable[Peter]
>>> -Changed from debug fprintfs to tracing[Jan]
>>
>> What were the issues that required the sysbus+PCI code you sent
>> previously? How did you address them in this series?
>
> Short answer: Those issues are not present in this patch.
>
> Long answer: The sysbus + PCI code is necessary for interrupt
> remapping to be implemented(it could also be done without sysbus + PCI
> code but that wouldn't be in line with the Intel IOMMU interrupt
> remapping code, which is already on the list). The idea is that X86
> IOMMUs should have a base class that implements common code. It was
> decided that this class should be a SysBusDev(which works perfectly
> with Intel IOMMU) but not with AMD IOMMU which has PCI properties. I
> had to find a way to provide for the PCI properties once I inherit
> from Intel IOMMU.
>
> In this patchset, I have not inherited from the base class(it's not
> merged yet) and even if it was merged I'd prefer to only use the
> SysBus + PCI code when necessary(when I work on interrupt remapping)
> so as to avoid delaying this patchset further.
We specifically came to the conclusion that it is better to evolve the
commodities between both IOMMU implementations (will be mostly about
interrupt remapping) in-tree rather than in separate patch sets outside
the mainline.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-06-15 17:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-15 12:21 [Qemu-devel] [V12 0/4] AMD IOMMU David Kiarie
2016-06-15 12:21 ` [Qemu-devel] [V12 1/4] hw/pci: Prepare for " David Kiarie
2016-06-22 19:53 ` Jan Kiszka
2016-06-15 12:21 ` [Qemu-devel] [V12 2/4] trace-events: Add AMD IOMMU trace events David Kiarie
2016-06-15 12:21 ` [Qemu-devel] [V12 3/4] hw/i386: Introduce AMD IOMMU David Kiarie
2016-06-22 20:24 ` Jan Kiszka
2016-07-04 5:06 ` David Kiarie
2016-07-04 5:41 ` Jan Kiszka
2016-07-04 5:49 ` David Kiarie
2016-07-04 5:57 ` Jan Kiszka
2016-07-08 7:01 ` David Kiarie
2016-07-08 9:51 ` Jan Kiszka
2016-06-15 13:15 ` [Qemu-devel] [V12 0/4] " Jan Kiszka
2016-06-15 14:26 ` Eduardo Habkost
2016-06-15 17:07 ` David Kiarie
2016-06-15 17:13 ` Jan Kiszka [this message]
[not found] ` <1465993312-18119-5-git-send-email-davidkiarie4@gmail.com>
2016-06-22 20:25 ` [Qemu-devel] [V12 4/4] hw/i386: AMD IOMMU IVRS table Jan Kiszka
2016-07-04 20:33 ` Michael S. Tsirkin
2016-07-08 7:05 ` 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=57618CC1.9000505@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=davidkiarie4@gmail.com \
--cc=ehabkost@redhat.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 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.