From: Ingo Molnar <mingo@kernel.org>
To: Stephane Eranian <eranian@google.com>
Cc: linux-kernel@vger.kernel.org, peterz@infradead.org,
ak@linux.intel.com, kan.liang@intel.com, jolsa@redhat.com,
vincent.weaver@maine.edu
Subject: Re: [PATCH v2] perf/x86/intel/ds: fix EVENT vs. UEVENT PEBS constraints
Date: Tue, 21 May 2019 10:26:11 +0200 [thread overview]
Message-ID: <20190521082611.GA34626@gmail.com> (raw)
In-Reply-To: <20190521005246.423-1-eranian@google.com>
* Stephane Eranian <eranian@google.com> wrote:
> This patch fixes an issue revealed by the following commit:
> Commit 6b89d4c1ae85 ("perf/x86/intel: Fix INTEL_FLAGS_EVENT_CONSTRAINT* masking")
>
> That patch modified INTEL_FLAGS_EVENT_CONSTRAINT() to only look at the event code
> when matching a constraint. If code+umask were needed, then the
> INTEL_FLAGS_UEVENT_CONSTRAINT() macro was needed instead.
> This broke with some of the constraints for PEBS events.
> Several of them, including the one used for cycles:p, cycles:pp, cycles:ppp
> fell in that category and caused the event to be rejected in PEBS mode.
> In other words, on some platforms a cmdline such as:
>
> $ perf top -e cycles:pp
>
> would fail with EINVAL.
>
> This patch fixes this issue by properly using INTEL_FLAGS_UEVENT_CONSTRAINT()
> when needed in the PEBS constraint tables.
>
> In v2:
> - add fixes for Core2, Nehalem, Silvermont, and Atom
>
> Reported-by: Ingo Molnar <mingo@kernel.org>
> Signed-off-by: Stephane Eranian <eranian@google.com>
> ---
> arch/x86/events/intel/ds.c | 28 ++++++++++++++--------------
> 1 file changed, 14 insertions(+), 14 deletions(-)
Thanks Stephane for the quick fixes!
Ingo
next prev parent reply other threads:[~2019-05-21 8:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-21 0:52 [PATCH v2] perf/x86/intel/ds: fix EVENT vs. UEVENT PEBS constraints Stephane Eranian
2019-05-21 8:26 ` Ingo Molnar [this message]
2019-05-21 8:28 ` [tip:perf/urgent] perf/x86/intel/ds: Fix " tip-bot for Stephane Eranian
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=20190521082611.GA34626@gmail.com \
--to=mingo@kernel.org \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.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 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.