mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Andi Kleen <ak@linux.intel.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
	linux-kernel@vger.kernel.org, tglx@linutronix.de,
	jolsa@redhat.com, eranian@google.com
Subject: Re: [PATCH V2 4/4] perf/x86: fix: disable userspace RDPMC usage for large PEBS
Date: Wed, 20 Dec 2017 17:05:29 -0500	[thread overview]
Message-ID: <f58e2ee8-9228-0c94-1954-c2ef7b6b46d1@linux.intel.com> (raw)
In-Reply-To: <20171220214147.GJ25156@tassilo.jf.intel.com>



On 12/20/2017 4:41 PM, Andi Kleen wrote:
> On Wed, Dec 20, 2017 at 11:42:51AM -0800, kan.liang@linux.intel.com wrote:
>> From: Kan Liang <kan.liang@linux.intel.com>
>>
>> The userspace RDPMC usage never works for large PEBS since the large
>> PEBS is introduced by
>> commit b8241d20699e ("perf/x86/intel: Implement batched PEBS interrupt
>> handling (large PEBS interrupt threshold)")
>>
>> When the PEBS interrupt threshold is larger than one, there is no way to
>> get exact auto-reload times and value for userspace RDPMC.
>>
>> Disable the userspace RDPMC usage when large PEBS is enabled.
> 
> The only drawback is that the event wraps quickly. 

It's broken. The value read from RDPMC command will always between 
-reload_val and 0. Without reload times, I think it's impossible to 
calculate the total count number.

> I suspect in many
> cases it's still usable for measuring short regions.
>

Unless the short region is less than reload_val.
Otherwise, reload times is needed.

Thanks,
Kan

> I wouldn't force disable it, just let the users deal with it.
> 
> -Andi
> 

      reply	other threads:[~2017-12-20 22:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-20 19:42 [PATCH V2 0/4] bug fix mmap read and rdpmc read in " kan.liang
2017-12-20 19:42 ` [PATCH V2 1/4] perf/x86/intel: fix event update for auto-reload kan.liang
2017-12-20 19:42 ` [PATCH V2 2/4] perf/x86: introduce read function for x86_pmu kan.liang
2017-12-20 19:42 ` [PATCH V2 3/4] perf/x86/intel: drain PEBS buffer in event read kan.liang
2017-12-20 19:42 ` [PATCH V2 4/4] perf/x86: fix: disable userspace RDPMC usage for large PEBS kan.liang
2017-12-20 21:41   ` Andi Kleen
2017-12-20 22:05     ` Liang, Kan [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=f58e2ee8-9228-0c94-1954-c2ef7b6b46d1@linux.intel.com \
    --to=kan.liang@linux.intel.com \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    /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