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


[Xen-devel] [RFC PATCH] Xen blkback for 2.6.40.

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] [RFC PATCH] Xen blkback for 2.6.40.
From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
Date: Mon, 18 Apr 2011 13:57:43 -0400
Delivery-date: Mon, 18 Apr 2011 11:02:38 -0700
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/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
I am proposing this patch for 2.6.40. This is an RFC at this point.

The git tree for this specific patch is

(the full tree is devel/xen-blkback-v3)

Please take a look at the patch. I know that I need to rewrite the description
to have more details for the upstream community - and that will be shortly 

Any thoughts on what I should address/remove/augment/etc would be appreciated. 
And whether
the code has any obvious pitfalls?

The code was originally lifted from 2.6.18, then ported to 2.6.32, and now I 
have backported
it to 2.6.38/.39. scripts/checkpatch.pl had been applied and also some 
re-ordering of the code
has been done to make it easier to read.

Xen-devel mailing list

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