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 | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/Osstest/Debian.pm b/Osstest/Debian.pm index 0f92661..3e56c1f 100644 --- a/Osstest/Debian.pm +++ b/Osstest/Debian.pm @@ -178,7 +178,8 @@ ext2load scsi 0 \\\${kernel_addr_r} $kern fdt mknod /chosen module\@0 fdt set /chosen/module\@0 compatible "xen,linux-zimage" "xen,multiboot-module" fdt set /chosen/module\@0 reg <\\\${kernel_addr_r} \\\${filesize}> -fdt set /chosen/module\@0 bootargs "$xenkopt ro root=$root" +# clk_ignore_unused is due to http://bugs.xenproject.org/xen/bug/45 +fdt set /chosen/module\@0 bootargs "$xenkopt ro root=$root clk_ignore_unused" echo Loaded $kern to \\\${kernel_addr_r} (\\\${filesize}) echo command line: $xenkopt ro root=$root -- 2.1.1 _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org http://lists.xen.org/xen-devel
