From: "Liang, Kan" <kan.liang@linux.intel.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, linux-kernel@vger.kernel.org,
tglx@linutronix.de, jolsa@redhat.com, eranian@google.com,
ak@linux.intel.com
Subject: Re: [PATCH 4/4] perf/x86/intel: drain PEBS buffer in event read
Date: Tue, 19 Dec 2017 15:10:04 -0500 [thread overview]
Message-ID: <f6c60815-e617-f26e-04a3-0749006ab540@linux.intel.com> (raw)
In-Reply-To: <20171219190214.zaqhmpz2rv2a5pgl@hirez.programming.kicks-ass.net>
On 12/19/2017 2:02 PM, Peter Zijlstra wrote:
> On Mon, Dec 18, 2017 at 03:34:51AM -0800, kan.liang@linux.intel.com wrote:
>> --- a/arch/x86/events/intel/ds.c
>> +++ b/arch/x86/events/intel/ds.c
>> @@ -926,6 +926,16 @@ void intel_pmu_pebs_del(struct perf_event *event)
>> pebs_update_state(needed_cb, cpuc, event->ctx->pmu);
>> }
>>
>> +void intel_pmu_pebs_read(struct perf_event *event)
>> +{
>> + struct cpu_hw_events *cpuc = this_cpu_ptr(&cpu_hw_events);
>> +
>> + if (pebs_needs_sched_cb(cpuc))
>> + return intel_pmu_drain_pebs_buffer();
>> +
>> + x86_perf_event_update(event, 0, 0);
>> +}
>
> This is completely broken.. what if @event isn't a pebs event, but we
> do have an auto-reloading pebs event configured?
>
precise_ip will be checked before intel_pmu_pebs_read is called.
So @event must be a pebs event.
@@ -2060,6 +2060,14 @@ static void intel_pmu_del_event(struct perf_event
*event)
intel_pmu_pebs_del(event);
}
+static void intel_pmu_read_event(struct perf_event *event)
+{
+ if (event->attr.precise_ip)
+ return intel_pmu_pebs_read(event);
+
+ x86_perf_event_update(event, 0, 0);
+}
prev parent reply other threads:[~2017-12-19 20:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-18 11:34 [PATCH 0/4] bug fix mmap read in large PEBS kan.liang
2017-12-18 11:34 ` [PATCH 1/4] perf/x86/intel: pass auto-reload information to event update kan.liang
2017-12-18 11:34 ` [PATCH 2/4] perf/x86/intel: fix event update for auto-reload kan.liang
2017-12-19 18:58 ` Peter Zijlstra
2017-12-19 20:08 ` Liang, Kan
2017-12-19 20:24 ` Liang, Kan
2017-12-19 22:07 ` Peter Zijlstra
2017-12-19 22:11 ` Andi Kleen
2017-12-19 23:25 ` Liang, Kan
2017-12-18 11:34 ` [PATCH 3/4] perf/x86: introduce read function for x86_pmu kan.liang
2017-12-18 11:34 ` [PATCH 4/4] perf/x86/intel: drain PEBS buffer in event read kan.liang
2017-12-19 19:02 ` Peter Zijlstra
2017-12-19 20:10 ` 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=f6c60815-e617-f26e-04a3-0749006ab540@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