From: Jan Kiszka <jan.kiszka@web.de>
To: Eduardo Habkost <ehabkost@redhat.com>,
David Kiarie <davidkiarie4@gmail.com>
Cc: qemu-devel@nongnu.org, imammedo@redhat.com, marcel@redhat.com,
mst@redhat.com, pbonzini@redhat.com, peterx@redhat.com,
wexu@redhat.com, alex.williamson@redhat.com, rkrcmar@redhat.com
Subject: Re: [Qemu-devel] [RFC] hw/i386: Composite Bus and PCI device
Date: Fri, 10 Jun 2016 07:30:24 +0200 [thread overview]
Message-ID: <575A5070.3060802@web.de> (raw)
In-Reply-To: <20160608152517.GK18662@thinpad.lan.raisama.net>
[-- Attachment #1: Type: text/plain, Size: 879 bytes --]
On 2016-06-08 17:25, Eduardo Habkost wrote:
> On Wed, Jun 08, 2016 at 01:00:32PM +0300, David Kiarie wrote:
>> Sample composite SysBus and PCI device similar to AMD IOMMU setup
>>
>> Signed-off-by: David Kiarie <davidkiarie4@gmail.com>
>> ---
>> hw/i386/compositedevice.c | 113 ++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 113 insertions(+)
>> create mode 100644 hw/i386/compositedevice.c
>
> The filename is very generic (hw/i386/compositedevice.c), but it
> has lots of AMD-specific names.
>
> Is your plan to provide generic helpers for implementing
> SysBus+PCI devices, or is it going to be inside a source file
> specific for AMD IOMMU?
As far as I understood - David, correct me - this patch is more of a
simplified demonstrator of the architecture to be applied on the actual
AMD IOMMU code. It is not for merge.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-06-10 5:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-08 10:00 [Qemu-devel] [RFC] AMD IOMMU: emulate multiple devices David Kiarie
2016-06-08 10:00 ` [Qemu-devel] [RFC] hw/i386: Composite Bus and PCI device David Kiarie
2016-06-08 15:25 ` Eduardo Habkost
2016-06-10 5:30 ` Jan Kiszka [this message]
2016-06-11 19:36 ` 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=575A5070.3060802@web.de \
--to=jan.kiszka@web.de \
--cc=alex.williamson@redhat.com \
--cc=davidkiarie4@gmail.com \
--cc=ehabkost@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rkrcmar@redhat.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).