From d9badc8e8b912dbfaf69d1979de380c43e0580ec Mon Sep 17 00:00:00 2001 From: Naga Chumbalkar Date: Tue, 23 Feb 2010 18:14:58 +0100 Subject: [PATCH] --- yaml --- r: 182278 b: refs/heads/master c: 8588d1067147e14d1dd521fbadd1d2564f8cc794 h: refs/heads/master v: v3 --- [refs] | 2 +- trunk/arch/x86/oprofile/op_x86_model.h | 9 +++++++++ 2 files changed, 10 insertions(+), 1 deletion(-) diff --git a/[refs] b/[refs] index f484b027e0e5..90d5080e29e1 100644 --- a/[refs] +++ b/[refs] @@ -1,2 +1,2 @@ --- -refs/heads/master: 98a2e73a0690b3610f049a64154d8145e5771713 +refs/heads/master: 8588d1067147e14d1dd521fbadd1d2564f8cc794 diff --git a/trunk/arch/x86/oprofile/op_x86_model.h b/trunk/arch/x86/oprofile/op_x86_model.h index 59fa2bdb0da3..ff82a755edd4 100644 --- a/trunk/arch/x86/oprofile/op_x86_model.h +++ b/trunk/arch/x86/oprofile/op_x86_model.h @@ -59,6 +59,15 @@ struct op_counter_config; static inline void op_x86_warn_in_use(int counter) { + /* + * The warning indicates an already running counter. If + * oprofile doesn't collect data, then try using a different + * performance counter on your platform to monitor the desired + * event. Delete counter #%d from the desired event by editing + * the /usr/share/oprofile/%s//events file. If the event + * cannot be monitored by any other counter, contact your + * hardware or BIOS vendor. + */ pr_warning("oprofile: counter #%d on cpu #%d may already be used\n", counter, smp_processor_id()); }