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] Re: [Qemu-devel] [PATCH 5/7] xen: add block device backe

To: Gerd Hoffmann <kraxel@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [Qemu-devel] [PATCH 5/7] xen: add block device backend driver.
From: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>
Date: Tue, 5 Aug 2008 12:36:32 +0100
Cc: Blue Swirl <blauwirbel@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, qemu-devel@xxxxxxxxxx
Delivery-date: Tue, 05 Aug 2008 04:36:55 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48983488.6010207@xxxxxxxxxx>
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>
Mail-followup-to: Samuel Thibault <samuel.thibault@xxxxxxxxxxxxx>, Gerd Hoffmann <kraxel@xxxxxxxxxx>, Blue Swirl <blauwirbel@xxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx, qemu-devel@xxxxxxxxxx
References: <1217865045-10722-1-git-send-email-kraxel@xxxxxxxxxx> <1217865045-10722-6-git-send-email-kraxel@xxxxxxxxxx> <f43fc5580808041026t49c8962fhe6ef926608e3db6c@xxxxxxxxxxxxxx> <48975D9A.7070109@xxxxxxxxxx> <20080804213456.GA4518@implementation> <4897F8AA.3060303@xxxxxxxxxx> <20080805104751.GN4478@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> <48983488.6010207@xxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.12-2006-07-14
Gerd Hoffmann, le Tue 05 Aug 2008 13:07:52 +0200, a écrit :
> Samuel Thibault wrote:
> > Gerd Hoffmann, le Tue 05 Aug 2008 08:52:26 +0200, a écrit :
> >>> There is: the info node, which is an OR of the
> >> Who sets that node?  Backend driver or xend?
> > 
> > backend, see linux/driver/xen/blkback/xenbus.c 
> Hmm, ok.
> mode="r" (in backend directory) means readonly, ok.
> device-type="cdrom" (backend dir too) means cdrom, ok.

These are set by xend, i.e. when they come from the config, indeed.

> removable can't be indicated to the backend via xenstore?

Doesn't look like it is possible.  Why would you want to do that?

> btw: Looks like blktap doesn't set any VDISK_* flags?

I guess that's because blktap doesn't have the information.  The "info"
node is information about the underlying source of data, detected by
the block backend, while "mode" and "device-type" are configured by the
user (and should override the "info" information I guess).


Xen-devel mailing list

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