From: Paolo Bonzini <pbonzini@redhat.com>
To: Lan Tianyu <tianyu.lan@intel.com>,
qemu-devel@nongnu.org, xen-devel@lists.xensource.com
Cc: chao.gao@intel.com, kevin.tian@intel.com,
anthony.perard@citrix.com, ehabkost@redhat.com,
marcel@redhat.com, mst@redhat.com, rth@twiddle.net,
sstabellini@kernel.org
Subject: Re: [Qemu-devel] [RFC PATCH 0/4] Qemu: Add Xen vIOMMU support
Date: Fri, 17 Mar 2017 15:48:53 +0100 [thread overview]
Message-ID: <1e1d1637-1cf8-2ad4-36e2-342aa21b100d@redhat.com> (raw)
In-Reply-To: <1489750157-17401-1-git-send-email-tianyu.lan@intel.com>
On 17/03/2017 12:29, Lan Tianyu wrote:
> This patchset is to add Xen vIOMMU device model and handle
> irq remapping stuffs. Xen vIOMMU emulation is in the Xen hypervisor
> and the new device module in Qemu works as hypercall wrappers to
> create and destroy vIOMMU in hypervisor.
>
> Xen only supports emulated I440 and so we enable vIOMMU with emulated
> I440 chipset. This works on Linux and Windows guest.
Any plans to change this? Why is Xen not able to use Q35 with Intel
IOMMU, with only special hooks for interrupt remapping?
Paolo
> Chao Gao (4):
> I440: Allow adding sysbus devices with -device on I440
> Xen: add a dummy vIOMMU to create/destroy vIOMMU in Xen
> xen-pt: bind/unbind interrupt remapping format MSI
> msi: taking interrupt format into consideration during judging a pirq
> is binded with a event channel
next prev parent reply other threads:[~2017-03-17 14:49 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-17 11:29 [Qemu-devel] [RFC PATCH 0/4] Qemu: Add Xen vIOMMU support Lan Tianyu
2017-03-17 11:29 ` [Qemu-devel] [RFC PATCH 1/4] I440: Allow adding sysbus devices with -device on I440 Lan Tianyu
2017-03-20 19:49 ` Eduardo Habkost
2017-03-21 0:36 ` Lan Tianyu
2017-03-17 11:29 ` [Qemu-devel] [RFC PATCH 2/4] Xen: add a dummy vIOMMU to create/destroy vIOMMU in Xen Lan Tianyu
2017-03-30 16:24 ` Anthony PERARD
2017-03-30 20:19 ` Chao Gao
2017-03-17 11:29 ` [Qemu-devel] [RFC PATCH 3/4] xen-pt: bind/unbind interrupt remapping format MSI Lan Tianyu
2017-03-30 16:51 ` Anthony PERARD
2017-03-30 20:31 ` Chao Gao
2017-03-17 11:29 ` [Qemu-devel] [RFC PATCH 4/4] msi: taking interrupt format into consideration during judging a pirq is binded with a event channel Lan Tianyu
2017-03-30 17:29 ` Anthony PERARD
2017-03-30 20:38 ` Chao Gao
2017-03-17 11:46 ` [Qemu-devel] [RFC PATCH 0/4] Qemu: Add Xen vIOMMU support no-reply
2017-03-17 14:48 ` Paolo Bonzini [this message]
2017-03-17 20:57 ` Stefano Stabellini
2017-03-20 2:40 ` Lan Tianyu
2017-03-20 11:38 ` Paolo Bonzini
2017-03-20 14:17 ` [Qemu-devel] [Xen-devel] " Roger Pau Monné
2017-03-20 14:35 ` Paolo Bonzini
2017-03-21 1:13 ` [Qemu-devel] " Lan Tianyu
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=1e1d1637-1cf8-2ad4-36e2-342aa21b100d@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony.perard@citrix.com \
--cc=chao.gao@intel.com \
--cc=ehabkost@redhat.com \
--cc=kevin.tian@intel.com \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
--cc=sstabellini@kernel.org \
--cc=tianyu.lan@intel.com \
--cc=xen-devel@lists.xensource.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).