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] [XM-TEST] block device write verify test 2nd att

On Wed, May 24, 2006 at 02:09:49PM +0100, Harry Butterworth wrote:

> > Modifying the ramdisk is not verboten,
> > but it is a right pain in the backside for everyone, particularly me 
> > because I
> > need to build a new one and upload it and all of its source (because of the
> > GPL) to xm-test.xensource.com.
> The current test is modifying the ramdisk to add `tee` (as well as fancy
> head which we don't need anymore).
> Are you going to accept the patch if it requires the addition of `tee`
> to the ramdisk?  Or should I change the test to read the data back in
> domU---which I was specifically trying to avoid.
> The problem with reading the data back in domU after having written it
> is that it might mask bugs in the block driver.  Reading the data back
> might cause it to be committed to the device where otherwise a bug might
> cause it to be lost.

I think that's a fair point, so yes, we'll have to rev the ramdisk anyway.


Xen-devel mailing list