[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH 2/3][RFC] MSI/MSI-X support for dom0/driver domain

  • To: <keir@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: "Jiang, Yunhong" <yunhong.jiang@xxxxxxxxx>
  • Date: Mon, 28 May 2007 16:01:41 +0800
  • Delivery-date: Mon, 28 May 2007 01:00:30 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aceg/mz7PRs/d4jlSeu7V67d+hYswQ==
  • Thread-topic: [PATCH 2/3][RFC] MSI/MSI-X support for dom0/driver domain

This patch adds msi/msi-x support for domain0.

In native Linux 2.6.18, instead of irq, it is vector that are used when
MSI is enabled. We change it to use irq still when msi is enabled (This
change also happened in 2.6.20 later native Linux).
Add functions to allocate irq.
These two changes are not needed if we update to 2.6.21 kernel.

Remove the ack function in domain0, since xen will do that for us.

1) Two phys_ops are added, First is physdev_msi_setup, to notify xen
that the vector is msi-irq type. The second is PHYSDEVOP_msi_format, to
get the msi format from xen side (mainly for target CPU), is it ok to
add them?

2) Current pirq is a global resource, how about make pirq be a
per-domain resource? 
Yunhong Jiang

Attachment: msi_xen_dom0.patch
Description: msi_xen_dom0.patch

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.