Re: [Xen-devel] PCI frontend/backend, pciif.h

To:	Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject:	Re: [Xen-devel] PCI frontend/backend, pciif.h
From:	Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date:	Fri, 27 Jun 2008 11:11:57 +0100
Cc:
Delivery-date:	Fri, 27 Jun 2008 03:12:25 -0700
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to:	<20080626153746.GI9147@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe:	<http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index:	AcjYPjsHecoydkQxEd2gYwAX8io7RQ==
Thread-topic:	[Xen-devel] PCI frontend/backend, pciif.h
User-agent:	Microsoft-Entourage/11.4.0.080122

On 26/6/08 16:37, "Samuel Thibault" <samuel.thibault@xxxxxxxxxxxxx> wrote:

> Hello,
> 
> Is there some documentation about the internals of PCI frontend/backend?

I don't think so.

> 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?

Yes, the headers are supposed to be self-contained.

 -- Keir

> Samuel
> 
> _______________________________________________
> 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

WARNING - OLD ARCHIVES

xen-devel

Re: [Xen-devel] PCI frontend/backend, pciif.h