dom0 is not aware that some clocks are actually in use (e.g. by the hypervisor), so this stops the kernel from messing with (specifically, disabling) those clocks. It's harmless even when not needed.
Really there ought to be some interface to communicate this from Xen to dom0, or some other mechanism to gate things. See http://bugs.xenproject.org/xen/bug/45 This bug is present in at least Wheezy and Jessie so apply this workaround to those. Signed-off-by: Ian Campbell <[email protected]> Acked-by: Ian Jackson <[email protected]> --- v5: Conditional on wheezy|jessie v3: More verbiage about why this is done v2: New patch, previously incorrectly included in "Osstest/Debian: Workaround oddities in the u-boot script parser." --- Osstest/Debian.pm | 3 +++ 1 file changed, 3 insertions(+) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index 146fa94..8b94913 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -151,6 +151,9 @@ sub setupboot_uboot ($$$) { my @xenkopt = uboot_common_kernel_bootargs($ho); push @xenkopt, $xenkopt; + # http://bugs.xenproject.org/xen/bug/45 + push @xenkopt, "clk_ignore_unused" + if $ho->{Suite} =~ m/wheezy|jessie/; $xenkopt = join ' ', @xenkopt; -- 2.1.4 _______________________________________________ Xen-devel mailing list [email protected] http://lists.xen.org/xen-devel
