From: kan.liang@linux.intel.com
To: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
linux-kernel@vger.kernel.org
Cc: tglx@linutronix.de, jolsa@redhat.com, eranian@google.com,
ak@linux.intel.com, Kan Liang <kan.liang@linux.intel.com>
Subject: [PATCH 2/4] perf/x86/intel: fix event update for auto-reload
Date: Mon, 18 Dec 2017 03:34:49 -0800 [thread overview]
Message-ID: <1513596891-12362-3-git-send-email-kan.liang@linux.intel.com> (raw)
In-Reply-To: <1513596891-12362-1-git-send-email-kan.liang@linux.intel.com>
From: Kan Liang <kan.liang@linux.intel.com>
There is bug when mmap read event->count with large PEBS enabled.
Here is an example.
#./read_count
0x71f0
0x122c0
0x1000000001c54
0x100000001257d
0x200000000bdc5
There is auto-reload mechanism enabled for PEBS events in fixed period
mode. But the calculation of event->count does not take the auto-reload
values into account. Anyone who read the event->count will get wrong
result, e.g x86_pmu_read. Also, the calculation of hwc->period_left is
wrong either. It impacts the accuracy of period for the first record in
PEBS multiple records.
The issue is introduced with the auto-reload mechanism enabled by
commit 851559e35fd5 ("perf/x86/intel: Use the PEBS auto reload mechanism
when possible")
For the auto-reload before the last time, it went through the whole
period (reload value) every time. So period * times should be added into
the event->count.
For the last load, the elapsed delta (event-)time need to be corrected
by adding the period (reload value). Because the start point is -period.
Signed-off-by: Kan Liang <kan.liang@linux.intel.com>
---
arch/x86/events/core.c | 14 ++++++++++++++
arch/x86/events/intel/ds.c | 8 +++++++-
2 files changed, 21 insertions(+), 1 deletion(-)
diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
index 35552ea..f74e21d 100644
--- a/arch/x86/events/core.c
+++ b/arch/x86/events/core.c
@@ -100,6 +100,20 @@ u64 x86_perf_event_update(struct perf_event *event,
* of the count.
*/
delta = (new_raw_count << shift) - (prev_raw_count << shift);
+
+ /*
+ * Take auto-reload into account
+ * For the auto-reload before the last time, it went through the
+ * whole period (reload_val) every time.
+ * Just simply add period * times to the event.
+ *
+ * For the last load, the elapsed delta (event-)time need to be
+ * corrected by adding the period. Because the start point is -period.
+ */
+ if (reload_times > 0) {
+ delta += (reload_val << shift);
+ local64_add(reload_val * (reload_times - 1), &event->count);
+ }
delta >>= shift;
local64_add(delta, &event->count);
diff --git a/arch/x86/events/intel/ds.c b/arch/x86/events/intel/ds.c
index 0b693b7..f0f6026 100644
--- a/arch/x86/events/intel/ds.c
+++ b/arch/x86/events/intel/ds.c
@@ -1256,11 +1256,17 @@ static void __intel_pmu_pebs_event(struct perf_event *event,
void *base, void *top,
int bit, int count)
{
+ struct hw_perf_event *hwc = &event->hw;
struct perf_sample_data data;
struct pt_regs regs;
void *at = get_next_pebs_record_by_bit(base, top, bit);
- if (!intel_pmu_save_and_restart(event, 0, 0) &&
+ /*
+ * Now, auto-reload is only enabled in fixed period mode.
+ * The reload value is always hwc->sample_period.
+ * May need to change it, if auto-reload is enabled in freq mode later.
+ */
+ if (!intel_pmu_save_and_restart(event, hwc->sample_period, count - 1) &&
!(event->hw.flags & PERF_X86_EVENT_AUTO_RELOAD))
return;
--
2.7.4
next prev parent reply other threads:[~2017-12-18 19:47 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 ` kan.liang [this message]
2017-12-19 18:58 ` [PATCH 2/4] perf/x86/intel: fix event update for auto-reload 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
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=1513596891-12362-3-git-send-email-kan.liang@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