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] block read verify patch for xm-test

To: Harry Butterworth <harry@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [PATCH] block read verify patch for xm-test
From: Ewan Mellor <ewan@xxxxxxxxxxxxx>
Date: Fri, 19 May 2006 16:30:51 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Fri, 19 May 2006 08:31:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1147454076.20292.2.camel@xxxxxxxxxxxxxxxxxxxxx>
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: <1147454076.20292.2.camel@xxxxxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.9i
On Fri, May 12, 2006 at 06:14:35PM +0100, Harry Butterworth wrote:

> >From the patch:
> +# This test initialises a ram disk in dom0 with data from /dev/urandom
> and
> +# then imports the ram disk device as a physical device into a domU.
> The md5
> +# checksum of the data in the ramdisk is calculated in dom0 and also
> +# calculated by the domU reading the data through the blk frontend and
> +# backend drivers.  The test succeeds if the checksums match indicating
> that
> +# the domU successfully read all the correct data from the device.
> Signed-off-by: Harry Butterworth <butterwo@xxxxxxxxxx>

Applied, thanks Harry.


Xen-devel mailing list

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