| commit | 5b02aa1e6e7cf7d3bbf8027dc7e05e0eb2f1e828 | |
| author | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Wed, 1 Feb 2012 21:07:41 +0000 (1 16:07 -0500) | ||
| committer | Konrad Rzeszutek Wilk <konrad.wilk@oracle.com> | |
| Fri, 3 Feb 2012 21:05:30 +0000 (3 16:05 -0500) | ||
| tree | 447c7f9a618aac8f6e8eb79dc7fa641c619232f8 | treesnapshot (tar.gz zip) |
| parent | 69e8f430e243d657c2053f097efebc2e2cd559f0 | commitdiff |
xen/bootup: During bootup suppress XENBUS: Unable to read cpu state
When the initial domain starts, it prints (depending on the
amount of CPUs) a slew of
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
which provide no useful information - as the error is a valid
issue - but not on the initial domain. The reason is that the
XenStore is not accessible at that time (it is after all the
first guest) so the CPU hotplug watch cannot parse "availability/cpu"
attribute.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
When the initial domain starts, it prints (depending on the
amount of CPUs) a slew of
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
XENBUS: Unable to read cpu state
which provide no useful information - as the error is a valid
issue - but not on the initial domain. The reason is that the
XenStore is not accessible at that time (it is after all the
first guest) so the CPU hotplug watch cannot parse "availability/cpu"
attribute.
Signed-off-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
| drivers/xen/cpu_hotplug.c | diffblobblamehistory |