| commit | e4184aaf3b2c4f2b69306f6cfc4bab8733c6c5f1 | |
| author | Daniel De Graaf <dgdegra@tycho.nsa.gov> | |
| Thu, 13 Oct 2011 20:07:08 +0000 (13 16:07 -0400) | ||
| committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Fri, 14 Oct 2011 13:25:18 +0000 (14 09:25 -0400) | ||
| tree | 0a7c8492040c7696a2fed05884fa71c6a494c40d | treesnapshot (tar.gz zip) |
| parent | 77447991b6c9aef83d101aae4a9e5d83c206b9c5 | commitdiff |
xenbus: don't rely on xen_initial_domain to detect local xenstore
The xenstore daemon does not have to run in the xen initial domain;
however, Linux currently uses xen_initial_domain to test if a loopback
event channel should be used instead of the event channel provided in
Xen's start_info structure. Instead, if the event channel passed in the
start_info structure is not valid, assume that this domain will run
xenstored locally and set up the event channel.
Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Reviewed-by: Ian Campbell <Ian.Campbell@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
The xenstore daemon does not have to run in the xen initial domain;
however, Linux currently uses xen_initial_domain to test if a loopback
event channel should be used instead of the event channel provided in
Xen's start_info structure. Instead, if the event channel passed in the
start_info structure is not valid, assume that this domain will run
xenstored locally and set up the event channel.
Signed-off-by: Daniel De Graaf <dgdegra@tycho.nsa.gov>
Reviewed-by: Ian Campbell <Ian.Campbell@citrix.com>
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
| drivers/xen/xenbus/xenbus_probe.c | diffblobblamehistory |