From: Peter Zijlstra <peterz@infradead.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Eduardo Valentin <eduval@amazon.com>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@redhat.com>, "H. Peter Anvin" <hpa@zytor.com>,
x86@kernel.org, Kan Liang <kan.liang@linux.intel.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
Jia Zhang <qianyue.zj@alibaba-inc.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCHv2 1/1] perf/x86/intel: make error messages less confusing
Date: Thu, 6 Sep 2018 09:21:49 +0200 [thread overview]
Message-ID: <20180906072149.GE24082@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20180905214707.GM27886@tassilo.jf.intel.com>
On Wed, Sep 05, 2018 at 02:47:07PM -0700, Andi Kleen wrote:
> On Wed, Sep 05, 2018 at 08:53:17AM -0700, Eduardo Valentin wrote:
> > On Wed, Sep 05, 2018 at 10:52:12AM +0200, Peter Zijlstra wrote:
> > > On Thu, Aug 23, 2018 at 08:07:32AM -0700, Eduardo Valentin wrote:
> > > > On a system with X86_FEATURE_ARCH_PERFMON disabled
> > > > and with a model not known by family PMU drivers,
> > > > user gets a kernel message log like the following:
> > > > [ 0.100114] Performance Events: unsupported p6 CPU model 85 no PMU driver, software events only.
> > > >
> > > > The "unsupported .. CPU" part may be confusing for some
> > > > users leading to wrong understanding that the kernel
> > > > does not support the CPU model.
> > >
> > > Send them back to first grade, such that they might learn to read?
> > >
> >
> > :-)
>
> I think it's a valid concern, I guess Eduardo actually has real people
> who got confused.
But it is really easy to confuse real people; as real people are mostly
clueless. There is only so much you can do for the semi illiterate
masses. Should we dumb down everything to baby talk just to cater to
them?
The string is clearly prefixed by the subsystem, if you get confused by
that your reading comprehension really is rock bottom.
[ 0.100114] Performance Events: unsupported p6 CPU model 85 no PMU driver, software events only.
Heck, it even mentions "no PMU driver", how much clues do you need?
Also, the proposed alternative:
[ 0.667154] Performance Events: CPU does not support PMU: no PMU driver, software events only.
Looses out information on which CPU family we failed on. Nor does it
mention the most likely reason for this error: virt crap.
I'd not mind a warning like:
[] Performance Events: Your crappy virt solution is lying about it's CPU model, it doesn't have a (matching) PMU.
next prev parent reply other threads:[~2018-09-06 7:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-23 15:07 Eduardo Valentin
2018-09-04 18:23 ` Eduardo Valentin
2018-09-04 23:02 ` Andi Kleen
2018-09-05 8:52 ` Peter Zijlstra
2018-09-05 15:53 ` Eduardo Valentin
2018-09-05 21:47 ` Andi Kleen
2018-09-06 7:21 ` Peter Zijlstra [this message]
2018-09-14 0:00 ` Eduardo Valentin
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=20180906072149.GE24082@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=ak@linux.intel.com \
--cc=dan.carpenter@oracle.com \
--cc=eduval@amazon.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpa@zytor.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=qianyue.zj@alibaba-inc.com \
--cc=tglx@linutronix.de \
--cc=x86@kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome