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 Signed-off-by: Ian Campbell <ian.campb...@citrix.com> --- 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 | 1 + 1 file changed, 1 insertion(+) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index c9e11fe..f03ece5 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -141,6 +141,7 @@ sub setupboot_uboot ($$$) { push @xenkopt, $xenkopt; push @xenkopt, "ro"; push @xenkopt, "root=$root"; + push @xenkopt, "clk_ignore_unused"; # http://bugs.xenproject.org/xen/bug/45 push @xenkopt, "rootdelay=$rootdelay" if $rootdelay; $xenkopt = join ' ', @xenkopt; -- 2.1.4 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
