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

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

The attached patches add MSI/MSI-x support for domain0/driver domain.

I have tried it on x86_64 host and at least my E1000 network card works.
Because some issues are not certain, especially for driver domain
support, so I do want to get some feedback before further work. 

The basic idea of the msi/msi-x support including:
1) Keep msi/msix configuration space access and msi-x mmio access in
domain0.
2) xen has no idea of msi/msi-x specific information, but will ack the
interrupt. A new interrupt type msi_irq_type is added, with similar
function as IOAPIC edge interrupt.
3) Keep PIRQ as a global resource controlled by domain0 (except those
owned by xen).

The new_file.patch just copy files that will be changed to sparse tree.
The msi_xen_dom0.patch support xen/domain0 side.
The msi_domU.patch support for driver domain.
I listed the issues in following mails.

Hope your feedback.

Thanks
Yunhong Jiang

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


 


Rackspace

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