Re: [Xen-devel] [PATCH 0/5] Add MSI support to xen environment

["Jan Beulich" <jbeulich@xxxxxxxxxx>]

As you are intending this not only for dom0, but also for domU - what are
the implications of a domU (intentionally or accidentally) programming the
address and/or data values to something other than the intended values?

Jan

>>> "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx> 25.10.07 18:46 >>>
Hi, 
The followed series patches add MSI support to xen environment. Please
have a look on it and give me any suggestion and I'd like to update
accordingly.

The basic idea including:
1) Keep vector global resource owned by xen, while split pirq into per
domain information.
2) domain0 kernel will operate msi resource for domain0/domU, while QEMU
will operate MSI resource for HVM domain.
3) Xen will do EOI for MSI interrupt.

pirq_per_domain.patch is mainly changes to xen source tree for
per-domain pirq.
domain_pirq_kernel.patch is changes to linux tree for per-domain pirq.

msi_irq_xen.patch changes xen to support msi for domain0/domainU.
msi_kernel.patch changes linux tree to support msi.

msi_passthrough.patch add msi support to passthrough hvm domain.

Signed-off-by: Yunhong Jiang <yunhong.jiang@xxxxxxxxx>

Thanks
Yunhong Jiang

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx 
http://lists.xensource.com/xen-devel


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel