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
..
xenbus	xen blkfront: Delay wait for block devices until after the disk is added	2008-04-24 23:57:33 +02:00
events.c	xen: add resend_irq_on_evtchn() definition into events.c	2008-04-24 23:57:32 +02:00
features.c	xen: move features.c from arch/x86/xen/features.c to drivers/xen	2008-04-24 23:57:32 +02:00
grant-table.c	xen: make grant table arch portable	2008-04-24 23:57:32 +02:00
Makefile	xen: import arch generic part of xencomm	2008-04-24 23:57:32 +02:00
xencomm.c	xen: import arch generic part of xencomm	2008-04-24 23:57:32 +02:00