 Home |
Products |
Support |
Community |
News |
xen-devel
[Xen-devel] PCI frontend/backend, pciif.h
| To: | xen-devel@xxxxxxxxxxxxxxxxxxx |
|---|---|
| Subject: | [Xen-devel] PCI frontend/backend, pciif.h |
| From: | Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx> |
| Date: | Thu, 26 Jun 2008 16:37:46 +0100 |
| Delivery-date: | Thu, 26 Jun 2008 08:38:11 -0700 |
| Envelope-to: | www-data@xxxxxxxxxxxxxxxxxx |
| List-help: | <mailto:xen-devel-request@lists.xensource.com?subject=help> |
| List-id: | Xen developer discussion <xen-devel.lists.xensource.com> |
| List-post: | <mailto:xen-devel@lists.xensource.com> |
| List-subscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe> |
| List-unsubscribe: | <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe> |
| Mail-followup-to: | Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx |
| Sender: | xen-devel-bounces@xxxxxxxxxxxxxxxxxxx |
| User-agent: | Mutt/1.5.12-2006-07-14 |
Hello, Is there some documentation about the internals of PCI frontend/backend? About pciif.h, it uses struct msix_entry from /usr/include/linux/pci.h, that is not really portable. Shouldn't it define it itself? Samuel _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [Xen-devel] [PATCH] xend: open qemu-dm log files in append mode, Ian Jackson |
|---|---|
| Next by Date: | Re: [Xen-devel] [PATCH] Log qemu-dm's message with date, time and pid, Daniel P. Berrange |
| Previous by Thread: | [Xen-devel] Linux kernel boot as-is, Asim |
| Next by Thread: | Re: [Xen-devel] PCI frontend/backend, pciif.h, Keir Fraser |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
