This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


To: <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-devel] YAIDTL
From: "Magenheimer, Dan (HP Labs Fort Collins)" <dan.magenheimer@xxxxxx>
Date: Thu, 16 Feb 2006 16:06:54 -0800
Cc: Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>, Rusty Russell <rusty@xxxxxxxxxxxxxxx>, hap9@xxxxxxxxxxxxxx
Delivery-date: Fri, 17 Feb 2006 00:19:26 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcYzRBdaLjwYRYEzRLyg0bW76BmWhAAEJJZg
Thread-topic: YAIDTL
I count this as the third recent attempt to add an abstraction
layer for interdomain page mapping/communication/transport.
(YAIDTL = yet another interdomain transport layer)

In addition, the ia64 port and the ppc port are struggling
(in some ways) with removing the x86-isms from the existing
blkif and netif backends.

Surely this is relevant to the core Xen developers?  And
surely when it is time to push the Xen drivers upstream,
the Linux driver community reviewers will notice the issue?

Inquiring minds want to know :-)

> Message: 2
> Date: Thu, 16 Feb 2006 16:56:31 -0500
> From: Ryan <hap9@xxxxxxxxxxxxxx>
> Subject: [Xen-devel] [PATCH][1/4] PCI Driver Domains: Xenbus
>       Convenience     Functions
> To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
> Message-ID: <1140126991.21373.17.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
> Content-Type: text/plain; charset="us-ascii"
> Resubmitting the driver domain patches against the latest 
> xen-unstable.
> These should apply cleanly to 8857:40d7eef7d3f5.
> In my digging through the existing backend/frontend drivers to plan my
> own, I found several places where code is duplicated to share and map
> pages via the grant tables. I added some convenience functions to
> xenbus_client.c to hide the details of the virtual address allocation
> and hypercall. My intent was to provide a simpler, higher-level
> interface for mapping in pages from another domain. While I believe
> these convenience functions simplify some typical uses of interdomain
> communication, they could easily be removed by expanding their uses in
> the PCI backend and frontend if there is opposition to their 
> inclusion.
> I also added a one-liner that causes xenbus_dev_(error|fatal) 
> to output
> to the kernel log buffer (and thus syslog) which was invaluable to me
> while debugging (by default, error messages only appear in xenstore).
> No significant changes since last submission.
> Signed-off-by: Ryan Wilson <hap9@xxxxxxxxxxxxxx>
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: xenbus-util.patch
> Type: text/x-patch
> Size: 7752 bytes
> Desc: not available
> Url : 
> http://lists.xensource.com/archives/html/xen-devel/attachments

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>