Re: [Xen-devel] [PATCH] block read verify patch for xm-test

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.

Ewan.

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

<Prev in Thread]	Current Thread	[Next in Thread>
[Xen-devel] [PATCH] block read verify patch for xm-test, Harry Butterworth Re: [Xen-devel] [PATCH] block read verify patch for xm-test, Ewan Mellor <=

Previous by Date:

[Xen-devel] Re: [PATCH][XM-TEST] Fix HVM disk.img file system size, Ewan Mellor

Next by Date:

Re: [Xen-devel] problem about changing state to XenbusStateClosed resulting in vbd entry removed from xenstore, Max Zhen

Previous by Thread:

[Xen-devel] [PATCH] block read verify patch for xm-test, Harry Butterworth

Next by Thread:

[Xen-devel] 4 Processors initialized but only one in /proc/cpuinfo, Stefan Berger

Indexes:

[Date] [Thread] [Top] [All Lists]