All of lore.kernel.org
 help / color / mirror / Atom feed
From: Taylor Andrews <andrewst@vmware.com>
To: Andi Kleen <andi@firstfloor.org>
Cc: "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: Mon, 7 Nov 2016 22:25:14 +0000	[thread overview]
Message-ID: <BN3PR0501MB1459CDCF7F91C63015AD9A0CA3A70@BN3PR0501MB1459.namprd05.prod.outlook.com> (raw)
In-Reply-To: <20161028163305.GD26852@two.firstfloor.org>

Hi Andi,

Do you know of any perf development-oriented mailing lists that may hold more information about this behavior of attempting to use in-use general purpose performance counters?  

Thanks,
Taylor

________________________________________
From: Andi Kleen <andi@firstfloor.org>
Sent: Friday, October 28, 2016 12:33 PM
To: Peter Zijlstra
Cc: Andi Kleen; Taylor Andrews; linux-perf-users@vger.kernel.org
Subject: Re: Question about Perf's handling of in-use performance counters

> But the thing is still racy, and therefore useless.

At least the Hypervisor case is not racy. The Hypervisor always
uses that counter.

-Andi

      parent reply	other threads:[~2016-11-07 22:26 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
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 [this message]

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=BN3PR0501MB1459CDCF7F91C63015AD9A0CA3A70@BN3PR0501MB1459.namprd05.prod.outlook.com \
    --to=andrewst@vmware.com \
    --cc=andi@firstfloor.org \
    --cc=linux-perf-users@vger.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 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.