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


Re: [Xen-devel] [PATCH][1/4] PCI Driver Domains: Xenbus Convenience Func

To: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH][1/4] PCI Driver Domains: Xenbus Convenience Functions
From: Ryan <hap9@xxxxxxxxxxxxxx>
Date: Mon, 30 Jan 2006 13:45:03 -0500
Delivery-date: Mon, 30 Jan 2006 18:54:31 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1138627445.8080.8.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <1138627445.8080.8.camel@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
On Mon, 2006-01-30 at 08:24 -0500, Ryan wrote:
> 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
> my 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).
> Signed-off-by: Ryan Wilson <hap9@xxxxxxxxxxxxxx>

Re-formatted to hopefully be more in line with Linux's CodingStyle.

Attachment: xenbus-util.patch
Description: Text Data

Xen-devel mailing list
<Prev in Thread] Current Thread [Next in Thread>