[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] [PATCH 1/2] xenbus: Fix loopback event channel assuming domain 0



The xenbus event channel established in xenbus_init is intended to be a
loopback channel, but the remote domain was hardcoded to 0; this will
cause the channel to be unusable when xenstore is not being run in
domain 0.

Signed-off-by: Daniel De Graaf <dgdegra@xxxxxxxxxxxxx>
Reviewed-by: Ian Campbell <Ian.Campbell@xxxxxxxxxx>
---
 drivers/xen/xenbus/xenbus_probe.c |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diff --git a/drivers/xen/xenbus/xenbus_probe.c 
b/drivers/xen/xenbus/xenbus_probe.c
index bd2f90c..82bf38c 100644
--- a/drivers/xen/xenbus/xenbus_probe.c
+++ b/drivers/xen/xenbus/xenbus_probe.c
@@ -712,7 +712,7 @@ static int __init xenbus_init(void)
 
                /* Next allocate a local port which xenstored can bind to */
                alloc_unbound.dom        = DOMID_SELF;
-               alloc_unbound.remote_dom = 0;
+               alloc_unbound.remote_dom = DOMID_SELF;
 
                err = HYPERVISOR_event_channel_op(EVTCHNOP_alloc_unbound,
                                                  &alloc_unbound);
-- 
1.7.6.4


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


 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.