tree ff1be4fa98c580cc3d3246d866b76102efa703cb
parent 10ca1e1ed58d6428924b5a44539334c341a6f485
author Michael Ellerman <[EMAIL PROTECTED]> Fri, 08 Jul 2005 07:56:35 -0700
committer Linus Torvalds <[EMAIL PROTECTED]> Fri, 08 Jul 2005 08:23:42 -0700
[PATCH] ppc64: Be consistent about printing which idle loop we're using
Not sure if we really need this, but it was handy to know which iSeries loop I
was testing.
Be consistent about printing which idle loop we're using, with this patch we
cover all cases.
Signed-off-by: Michael Ellerman <[EMAIL PROTECTED]>
Signed-off-by: Anton Blanchard <[EMAIL PROTECTED]>
Signed-off-by: Andrew Morton <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds <[EMAIL PROTECTED]>
arch/ppc64/kernel/iSeries_setup.c | 7 +++++--
arch/ppc64/kernel/setup.c | 4 +++-
2 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/arch/ppc64/kernel/iSeries_setup.c
b/arch/ppc64/kernel/iSeries_setup.c
--- a/arch/ppc64/kernel/iSeries_setup.c
+++ b/arch/ppc64/kernel/iSeries_setup.c
@@ -946,9 +946,12 @@ void __init iSeries_early_setup(void)
ppc_md.calibrate_decr = iSeries_calibrate_decr;
ppc_md.progress = iSeries_progress;
- if (get_paca()->lppaca.shared_proc)
+ if (get_paca()->lppaca.shared_proc) {
ppc_md.idle_loop = iseries_shared_idle;
- else
+ printk(KERN_INFO "Using shared processor idle loop\n");
+ } else {
ppc_md.idle_loop = iseries_dedicated_idle;
+ printk(KERN_INFO "Using dedicated idle loop\n");
+ }
}
diff --git a/arch/ppc64/kernel/setup.c b/arch/ppc64/kernel/setup.c
--- a/arch/ppc64/kernel/setup.c
+++ b/arch/ppc64/kernel/setup.c
@@ -1081,8 +1081,10 @@ void __init setup_arch(char **cmdline_p)
ppc_md.setup_arch();
/* Use the default idle loop if the platform hasn't provided one. */
- if (NULL == ppc_md.idle_loop)
+ if (NULL == ppc_md.idle_loop) {
ppc_md.idle_loop = default_idle;
+ printk(KERN_INFO "Using default idle loop\n");
+ }
paging_init();
ppc64_boot_msg(0x15, "Setup Done");
-
To unsubscribe from this list: send the line "unsubscribe bk-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
