From: Andi Kleen <ak@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Stephane Eranian <eranian@google.com>,
LKML <linux-kernel@vger.kernel.org>,
"mingo@elte.hu" <mingo@elte.hu>,
Arnaldo Carvalho de Melo <acme@redhat.com>,
Jiri Olsa <jolsa@redhat.com>
Subject: Re: [PATCH 2/2] perf: SNB exclusive PMU access for INST_RETIRED:PREC_DIST
Date: Fri, 19 Oct 2012 10:20:18 -0700 [thread overview]
Message-ID: <20121019172018.GA2095@tassilo.jf.intel.com> (raw)
In-Reply-To: <1350665152.2768.41.camel@twins>
> > > This isn't limited to admin, right? So the above turns into a DoS on the
> > > console.
> > >
> > Ok, so how about a WARN_ON_ONCE() instead?
>
> That should be fine I guess ;-)
imho there is need for a generic mechanism to return an error string
to the user program without such hacks.
-Andi
--
ak@linux.intel.com -- Speaking for myself only
next prev parent reply other threads:[~2012-10-19 17:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-19 14:52 [PATCH 0/2] perf: enforce exclusive PMU access for SNB INST_RETIRED:PREC_DIST Stephane Eranian
2012-10-19 14:52 ` [PATCH 1/2] perf tools: add event modifier to request exclusive PMU access Stephane Eranian
2012-10-19 15:13 ` Peter Zijlstra
2012-10-19 15:17 ` Stephane Eranian
2012-10-19 15:23 ` Jiri Olsa
2012-10-19 15:47 ` Stephane Eranian
2012-10-19 15:53 ` Jiri Olsa
2012-10-19 15:58 ` Stephane Eranian
2012-10-19 15:46 ` Andi Kleen
2012-10-19 16:07 ` Jiri Olsa
2012-10-19 14:52 ` [PATCH 2/2] perf: SNB exclusive PMU access for INST_RETIRED:PREC_DIST Stephane Eranian
2012-10-19 15:49 ` Andi Kleen
2012-10-19 15:58 ` Stephane Eranian
2012-10-19 16:27 ` Peter Zijlstra
2012-10-19 16:31 ` Stephane Eranian
2012-10-19 16:45 ` Peter Zijlstra
2012-10-19 17:20 ` Andi Kleen [this message]
2012-10-21 16:55 ` Ingo Molnar
2012-10-21 17:54 ` Stephane Eranian
2012-10-21 18:03 ` Ingo Molnar
2012-10-22 11:31 ` Stephane Eranian
2012-10-24 8:15 ` Ingo Molnar
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=20121019172018.GA2095@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@redhat.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.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