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

[Xen-devel] [PATCH 3/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:43 +0800
  • Delivery-date: Mon, 28 May 2007 01:01:57 -0700
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: Aceg/m5IM8RRXrEdSmifq6rbFr14Yw==
  • Thread-topic: [PATCH 3/3][RFC] MSI/MSI-X support for dom0/driver domain

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

The pci front end will use pci_ops to communicate with pci backend to
enable/disable msi/msi-x. Also access permission for MSI-x mmio range is
removed for the domain, and irq permission is added.

1) Current irq-permission is setup through domctl interface, which can
only be called from tools, while when we allocate irq for driver domain,
we need change the irq permission in kernel side, so I add a new
physdev_op to do this, is that ok?
2) Curretly the pci_enable_msi/msi-x and pci_disable_msi/msi-x
implementation are different for pci frontend. This cause problem if
both pci backend/frontend are enabled. A better method is to check if a
device is pci frontend device or a normal device and do different code,
but I didn't find an easy method to check if a device is a pci
frontend/backend device.

Yunhong Jiang

Attachment: msi_domU.patch
Description: msi_domU.patch

Xen-devel mailing list



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