Christian Limpach 1d78d70556 xen blkfront: Delay wait for block devices until after the disk is added ... When the xen block frontend driver is built as a module the module load is only synchronous up to the point where the frontend and the backend become connected rather than when the disk is added. This means that there can be a race on boot between loading the module and loading the dm-* modules and doing the scan for LVM physical volumes (all in the initrd). In the failure case the disk is not present until after the scan for physical volumes is complete. Taken from: http://xenbits.xensource.com/linux-2.6.18-xen.hg?rev/11483a00c017 Signed-off-by: Christian Limpach <Christian.Limpach@xensource.com> Signed-off-by: Mark McLoughlin <markmc@redhat.com> Signed-off-by: Jeremy Fitzhardinge <jeremy.fitzhardinge@citrix.com> Signed-off-by: Ingo Molnar <mingo@elte.hu> Signed-off-by: Thomas Gleixner <tglx@linutronix.de>		2008-04-24 23:57:33 +02:00
..
Makefile
xenbus_client.c	xen: replace callers of alloc_vm_area()/free_vm_area() with xen_ prefixed one	2008-04-24 23:57:32 +02:00
xenbus_comms.c
xenbus_comms.h
xenbus_probe.c	xen blkfront: Delay wait for block devices until after the disk is added	2008-04-24 23:57:33 +02:00
xenbus_probe.h
xenbus_xs.c