linux-perf-users.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andi Kleen <andi@firstfloor.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Andi Kleen <andi@firstfloor.org>,
	Taylor Andrews <andrewst@vmware.com>,
	"linux-perf-users@vger.kernel.org"
	<linux-perf-users@vger.kernel.org>
Subject: Re: Question about Perf's handling of in-use performance counters
Date: Fri, 28 Oct 2016 08:40:12 -0700	[thread overview]
Message-ID: <20161028154012.GC26852@two.firstfloor.org> (raw)
In-Reply-To: <20161028140354.GH3142@twins.programming.kicks-ass.net>

> No, it was about the (mis)guide-line having fundamental races and the
> belief that the BIOS has no business what so ever using these resources
> to begin with.

In this case it's not the BIOS, but a hypervisor who allocates the
counter. I believe there are valid use cases here. 

The same issue can also happen when people use user space perfmon
tools, like PCM or likwid, and potentially with other non BIOS users.

-Andi

  reply	other threads:[~2016-10-28 15:40 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-21 21:59 Question about Perf's handling of in-use performance counters Taylor Andrews
2016-10-27 18:11 ` Andi Kleen
2016-10-27 21:00   ` Peter Zijlstra
2016-10-28 13:53     ` Andi Kleen
2016-10-28 14:03       ` Peter Zijlstra
2016-10-28 15:40         ` Andi Kleen [this message]
2016-10-28 16:28           ` Peter Zijlstra
2016-10-28 16:33             ` Andi Kleen
2016-10-28 18:28               ` Taylor Andrews
2016-11-30 15:44                 ` Taylor Andrews
2016-11-30 18:17                   ` Peter Zijlstra
2016-11-07 22:25               ` Taylor Andrews

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=20161028154012.GC26852@two.firstfloor.org \
    --to=andi@firstfloor.org \
    --cc=andrewst@vmware.com \
    --cc=linux-perf-users@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).