WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

[Xen-devel] Userland blkback?

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Userland blkback?
From: Pim van Riezen <pi+lists@xxxxxxxxxxxx>
Date: Thu, 11 Aug 2011 14:53:47 +0200
Delivery-date: Thu, 11 Aug 2011 05:55:08 -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
Good day,

I'm toying around with a kernel mode caching layer that, at the moment, crashes 
into the ground if the driver is called from kernel space. I've been toying 
around with pvops dom0 kernels in the 2.6.3x family with the understanding that 
their lack of xen-blkback module would lead to an automatic fallback to a 
userspace blockdevice backend. Is there a secret switch to Xen 4.0/4.1 I need 
to be aware of to make this magic happen? Or is this a missing feature and  
does every pvops dom0-kernel that is not 3.0.1 need backports for xen-blkback?

Cheers,
Pim van Riezen


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

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