From: Jan Kiszka <jan.kiszka@siemens.com>
To: Peter Xu <peterx@redhat.com>, Rita Sinha <rita.sinha89@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] i386: Interrupt remapping support for VT-d
Date: Fri, 11 Mar 2016 08:28:02 +0100 [thread overview]
Message-ID: <56E27382.3010007@siemens.com> (raw)
In-Reply-To: <20160310052846.GB25832@pxdev.xzpeter.org>
On 2016-03-10 06:28, Peter Xu wrote:
> On Wed, Mar 09, 2016 at 12:58:17AM +0530, Rita Sinha wrote:
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>>
>> Still a bit hacky, unconditionally enabled (must become opt-in, not
>> available with in-kernel irqchip), not reporting faults properly - but
>> it works! And revealed a Linux bug [1]
>
> If the patch is to be merged finally, shall we better add a
> parameter to disable this feature for people do not need this?
Yes, we need a switch. The original IOMMU in the Q35 chipset doesn't
support IR, and already to be emulation-wise precise, we should allow to
user to turn this off (or on).
> Also, shall we make sure:
>
> - make sure patches' in-reply-to are correct (so that it's in a
> series, as mentioned by Eric before)
> - remove useless lines like "/* printf(...) */"
> - add one-line subject for each patch (possibly)?
> - ...
>
> [...]
>
>> diff --git a/hw/pci-host/q35.c b/hw/pci-host/q35.c
>> index 566e3d8..f7adc8e 100644
>> --- a/hw/pci-host/q35.c
>> +++ b/hw/pci-host/q35.c
>> @@ -431,6 +431,17 @@ static AddressSpace *q35_host_dma_iommu(PCIBus *bus, void *opaque, int devfn)
>> assert(0 <= devfn && devfn <= VTD_PCI_DEVFN_MAX);
>>
>> vtd_as = vtd_find_add_as(s, bus, devfn);
>> +
>> + memory_region_init_iommu(&vtd_as->iommu, OBJECT(s),
>> + &s->iommu_ops, "intel_iommu", UINT64_MAX);
>> + address_space_init(&vtd_as->as,
>> + &vtd_as->iommu, "intel_iommu");
>> + memory_region_init_io(&vtd_as->int_remap_region, OBJECT(s),
>> + &vtd_int_remap_ops, vtd_as,
>> + "intel_int_remap", UINT64_MAX);
>> + address_space_init(&vtd_as->int_remap_as,
>> + &vtd_as->int_remap_region,
>> + "intel_int_remap");
>
> One more thing... vtd_as->{as|iommu} should have been inited in
> vtd_find_add_as() already.
>
Good point. Logical merge artefact.
Jan
--
Siemens AG, Corporate Technology, CT RDA ITP SES-DE
Corporate Competence Center Embedded Linux
prev parent reply other threads:[~2016-03-11 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-08 19:28 [Qemu-devel] [PATCH 2/2] i386: Interrupt remapping support for VT-d Rita Sinha
2016-03-10 5:28 ` Peter Xu
2016-03-11 7:28 ` Jan Kiszka [this message]
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=56E27382.3010007@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=peterx@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rita.sinha89@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.