From: Peter Xu <peterx@redhat.com>
To: David Kiarie <davidkiarie4@gmail.com>
Cc: Eduardo Habkost <ehabkost@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
imammedo@redhat.com, jasowang@redhat.com,
Marcel Apfelbaum <marcel@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
pbonzini@redhat.com, Jan Kiszka <jan.kiszka@web.de>,
rkrcmar@redhat.com, alex.williamson@redhat.com, wexu@redhat.com,
Valentine Sinitsyn <valentine.sinitsyn@gmail.com>
Subject: Re: [Qemu-devel] [RFC] Allow AMD IOMMU to have both SysBusDevice and PCIDevice properties.
Date: Wed, 8 Jun 2016 10:17:04 +0800 [thread overview]
Message-ID: <20160608021704.GH1039@pxdev.xzpeter.org> (raw)
In-Reply-To: <CABdVeAC4vGbwX1OOPnm+OVZ57zLV8QLkH4Li+cwv6xPQ+4Yuow@mail.gmail.com>
On Tue, Jun 07, 2016 at 10:32:34PM +0300, David Kiarie wrote:
> On Tue, Jun 7, 2016 at 10:12 PM, Eduardo Habkost <ehabkost@redhat.com> wrote:
> > Hi,
>
> Hello,
>
> >
> > I didn't review the amd_iommu.c code, but there seems to be some
> > unrelated changes in the patch:
>
> Thanks for looking at this but I actually wanted someone to look at
> the amd_iommu.c. I mentioned in annotation that there are some
> unrelated changes because this work is based on code that has not been
> merged yet. I specifically sent this to have a review in amd_iommu.c
> not the details but the design. I have patchset that implements AMD
> IOMMU (translation only) which is implemented as a PCI device. It is
> however not possible to work on interrupt remapping without converting
> AMD IOMMU from a PCI device to a SysBusDevice. This device(AMD IOMMU),
> the one on this patch unlike in previous patches, creates to devices ;
> a PCI device and a SySBusDev which am not sure is acceptable.
I would suggest that you generate another patch, only contains the
changes you made related to adding the PCI device for AMD IOMMU,
explain bits about what this work is based on (e.g., IMHO it could be
based on your v11 AMD patchset and several other patches like Intel
IOMMU IR, just mention them in the cover letter), then mark it as a
RFC.
-- peterx
next prev parent reply other threads:[~2016-06-08 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-05 16:54 [Qemu-devel] [RFC] AMD IOMMU: emulate multiple devices David Kiarie
2016-06-05 16:54 ` [Qemu-devel] [RFC] Allow AMD IOMMU to have both SysBusDevice and PCIDevice properties David Kiarie
2016-06-07 19:12 ` Eduardo Habkost
2016-06-07 19:32 ` David Kiarie
2016-06-08 2:17 ` Peter Xu [this message]
2016-06-09 13:23 ` Marcel Apfelbaum
2016-06-11 12:01 ` 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=20160608021704.GH1039@pxdev.xzpeter.org \
--to=peterx@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=davidkiarie4@gmail.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=jan.kiszka@web.de \
--cc=jasowang@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.com \
--cc=valentine.sinitsyn@gmail.com \
--cc=wexu@redhat.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).