path: root/include/xen/xenbus.h
diff options
authorChristian Limpach <Christian.Limpach@xensource.com>2008-04-02 10:54:04 -0700
committerIngo Molnar <mingo@elte.hu>2008-04-24 23:57:33 +0200
commit1d78d7055629e3f6300d6b8d7028259ee2bffc0e (patch)
tree20bf47ccdd80ead20c69f8a536849c9cf8dd3223 /include/xen/xenbus.h
parent53f0e8afcb0d57cfaff06b89eb8b5302f167577e (diff)
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>
Diffstat (limited to 'include/xen/xenbus.h')
1 files changed, 1 insertions, 0 deletions
diff --git a/include/xen/xenbus.h b/include/xen/xenbus.h
index 6f7c290651a..6369d89c25d 100644
--- a/include/xen/xenbus.h
+++ b/include/xen/xenbus.h
@@ -97,6 +97,7 @@ struct xenbus_driver {
int (*uevent)(struct xenbus_device *, char **, int, char *, int);
struct device_driver driver;
int (*read_otherend_details)(struct xenbus_device *dev);
+ int (*is_ready)(struct xenbus_device *dev);
static inline struct xenbus_driver *to_xenbus_driver(struct device_driver *drv)