From: "tip-bot2 for Alexander Antonov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Alexander Antonov <alexander.antonov@linux.intel.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Kan Liang <kan.liang@linux.intel.com>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: perf/urgent] perf/x86/intel/uncore: Fix IIO event constraints for Skylake Server
Date: Wed, 17 Nov 2021 13:59:53 -0000 [thread overview]
Message-ID: <163715759351.11128.8247170608950065417.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20211115090334.3789-3-alexander.antonov@linux.intel.com>
The following commit has been merged into the perf/urgent branch of tip:
Commit-ID: 3866ae319c846a612109c008f43cba80b8c15e86
Gitweb: https://git.kernel.org/tip/3866ae319c846a612109c008f43cba80b8c15e86
Author: Alexander Antonov <alexander.antonov@linux.intel.com>
AuthorDate: Mon, 15 Nov 2021 12:03:33 +03:00
Committer: Peter Zijlstra <peterz@infradead.org>
CommitterDate: Wed, 17 Nov 2021 14:48:43 +01:00
perf/x86/intel/uncore: Fix IIO event constraints for Skylake Server
According to the latest uncore document, COMP_BUF_OCCUPANCY (0xd5) event
can be collected on 2-3 counters. Update uncore IIO event constraints for
Skylake Server.
Fixes: cd34cd97b7b4 ("perf/x86/intel/uncore: Add Skylake server uncore support")
Signed-off-by: Alexander Antonov <alexander.antonov@linux.intel.com>
Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
Reviewed-by: Kan Liang <kan.liang@linux.intel.com>
Link: https://lore.kernel.org/r/20211115090334.3789-3-alexander.antonov@linux.intel.com
---
arch/x86/events/intel/uncore_snbep.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/x86/events/intel/uncore_snbep.c b/arch/x86/events/intel/uncore_snbep.c
index e5ee6bb..9aba4ef 100644
--- a/arch/x86/events/intel/uncore_snbep.c
+++ b/arch/x86/events/intel/uncore_snbep.c
@@ -3678,6 +3678,7 @@ static struct event_constraint skx_uncore_iio_constraints[] = {
UNCORE_EVENT_CONSTRAINT(0xc0, 0xc),
UNCORE_EVENT_CONSTRAINT(0xc5, 0xc),
UNCORE_EVENT_CONSTRAINT(0xd4, 0xc),
+ UNCORE_EVENT_CONSTRAINT(0xd5, 0xc),
EVENT_CONSTRAINT_END
};
next prev parent reply other threads:[~2021-11-17 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 9:03 [RESEND PATCH v2 0/3] Several fixes for event constraints on SKX and SNR platforms alexander.antonov
2021-11-15 9:03 ` [RESEND PATCH v2 1/3] Fix filter_tid mask for CHA events on Skylake Server alexander.antonov
2021-11-17 13:59 ` [tip: perf/urgent] perf/x86/intel/uncore: " tip-bot2 for Alexander Antonov
2021-11-15 9:03 ` [RESEND PATCH v2 2/3] Fix IIO event constraints for " alexander.antonov
2021-11-17 13:59 ` tip-bot2 for Alexander Antonov [this message]
2021-11-15 9:03 ` [RESEND PATCH v2 3/3] Fix IIO event constraints for Snowridge alexander.antonov
2021-11-17 13:59 ` [tip: perf/urgent] perf/x86/intel/uncore: " tip-bot2 for Alexander Antonov
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=163715759351.11128.8247170608950065417.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=alexander.antonov@linux.intel.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=x86@kernel.org \
/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.