From: Peter Zijlstra <peterz@infradead.org>
To: "Liang, Kan" <kan.liang@linux.intel.com>
Cc: Vince Weaver <vincent.weaver@maine.edu>,
mingo@redhat.com, linux-kernel@vger.kernel.org, acme@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@redhat.com, namhyung@kernel.org, eranian@google.com,
ak@linux.intel.com, stable@vger.kernel.org
Subject: Re: [PATCH] Revert "perf/x86: Allow zero PEBS status with only single active event"
Date: Wed, 3 Mar 2021 21:21:31 +0100 [thread overview]
Message-ID: <YD/vy2RnkWZYiJHP@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <9484ab6e-a6e5-bb72-106f-ed904e50fc0c@linux.intel.com>
On Wed, Mar 03, 2021 at 02:53:00PM -0500, Liang, Kan wrote:
> On 3/3/2021 1:59 PM, Peter Zijlstra wrote:
> > On Wed, Mar 03, 2021 at 05:42:18AM -0800, kan.liang@linux.intel.com wrote:
> > > +++ b/arch/x86/events/intel/ds.c
> > > @@ -2000,18 +2000,6 @@ static void intel_pmu_drain_pebs_nhm(struct pt_regs *iregs, struct perf_sample_d
> > > continue;
> > > }
> > > - /*
> > > - * On some CPUs the PEBS status can be zero when PEBS is
> > > - * racing with clearing of GLOBAL_STATUS.
> > > - *
> > > - * Normally we would drop that record, but in the
> > > - * case when there is only a single active PEBS event
> > > - * we can assume it's for that event.
> > > - */
> > > - if (!pebs_status && cpuc->pebs_enabled &&
> > > - !(cpuc->pebs_enabled & (cpuc->pebs_enabled-1)))
> > > - pebs_status = cpuc->pebs_enabled;
> >
> > Wouldn't something like:
> >
> > pebs_status = p->status = cpus->pebs_enabled;
> >
>
> I didn't consider it as a potential solution in this patch because I don't
> think it's a proper way that SW modifies the buffer, which is supposed to be
> manipulated by the HW.
Right, but then HW was supposed to write sane values and it doesn't do
that either ;-)
> It's just a personal preference. I don't see any issue here. We may try it.
So I mostly agree with you, but I think it's a shame to unsupport such
chips, HSW is still a plenty useable chip today.
next prev parent reply other threads:[~2021-03-04 0:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-03 13:42 kan.liang
2021-03-03 18:59 ` Peter Zijlstra
2021-03-03 19:53 ` Liang, Kan
2021-03-03 20:21 ` Peter Zijlstra [this message]
2021-03-16 7:22 ` Namhyung Kim
2021-03-16 12:28 ` Liang, Kan
2021-03-16 18:34 ` Stephane Eranian
2021-03-16 19:36 ` Liang, Kan
2021-03-17 2:04 ` Namhyung Kim
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=YD/vy2RnkWZYiJHP@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=acme@kernel.org \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=stable@vger.kernel.org \
--cc=vincent.weaver@maine.edu \
/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
all inboxes | Powered by JetHome®