All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@kernel.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Ingo Molnar <mingo@kernel.org>,
	Adrian Hunter <adrian.hunter@intel.com>,
	Andy Lutomirski <luto@amacapital.net>,
	Vince Weaver <vincent.weaver@maine.edu>,
	Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@linux.intel.com>,
	linux-kernel@vger.kernel.org, Jiri Olsa <jolsa@redhat.com>,
	Stephane Eranian <eranian@google.com>,
	Borislav Petkov <bp@suse.de>,
	Alexander Shishkin <alexander.shishkin@linux.intel.com>,
	Andi Kleen <ak@linux.intel.com>
Subject: Re: [RFC PATCH] perf: Provide status of known PMUs
Date: Thu, 9 Jul 2015 11:47:49 -0300	[thread overview]
Message-ID: <20150709144749.GA19430@kernel.org> (raw)
In-Reply-To: <20150709124257.GU19282@twins.programming.kicks-ass.net>

Em Thu, Jul 09, 2015 at 02:42:57PM +0200, Peter Zijlstra escreveu:
> On Thu, Jul 09, 2015 at 02:32:05PM +0200, Ingo Molnar wrote:

> >    perf record error: The 'bts' PMU is not available, because the CPU does not support it
 
> This one makes sense.
 
> >    perf record error: The 'bts' PMU is not available, because this architecture does not support it
> >    perf record error: The 'bts' PMU is not available, because its driver is not built into the kernel

> > Because if it's the wrong architecture or CPU, I look for a box with
> > the right one, if it's simply the kernel not having the necessary
> > PMU driver then I'll boot a kernel with it enabled.
 
> These not so much; why won't a generic: "Unknown PMU, check
> arch/kernel" do?
 
> The thing is, I hate that hard-coded list, its pain I don't need.

Well, then we need to have tooling looking around and having tables to
provide those more precise error messages, which we want to have.

I guess we can do parts of that by looking at info already exported by
the kernel, /proc/cpuinfo stuff, etc. But "Unknown PMU, check
arch/kernel" is way too vague :-\

- Arnaldo

  reply	other threads:[~2015-07-09 14:48 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  7:48 [RFC PATCH] perf: Provide status of known PMUs Adrian Hunter
2015-07-09  8:10 ` Ingo Molnar
2015-07-09  8:44   ` Adrian Hunter
2015-07-09  8:50 ` Peter Zijlstra
2015-07-09  9:26   ` Ingo Molnar
2015-07-09 11:59     ` Peter Zijlstra
2015-07-09 12:32       ` Ingo Molnar
2015-07-09 12:42         ` Peter Zijlstra
2015-07-09 14:47           ` Arnaldo Carvalho de Melo [this message]
2015-07-10  8:35           ` Ingo Molnar
2015-07-10 18:59             ` Stephane Eranian
2015-07-09  9:30   ` Adrian Hunter
2015-07-09 11:44     ` Peter Zijlstra

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150709144749.GA19430@kernel.org \
    --to=acme@kernel.org \
    --cc=adrian.hunter@intel.com \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=bp@suse.de \
    --cc=eranian@google.com \
    --cc=hpa@linux.intel.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@amacapital.net \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=vincent.weaver@maine.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.