Received-SPF: pass (google.com: domain of linux-kernel+bounces-81887-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:4601:e00::3 as permitted sender) client-ip=2604:1380:4601:e00::3;
From: Namhyung Kim <namhyung@kernel.org>
To: linux-kernel@vger.kernel.org,
	Mark Rutland <mark.rutland@arm.com>
Cc: linux-perf-users@vger.kernel.org,
	leo.yan@linaro.org,
	suzuki.poulose@arm.com,
	acme@redhat.com,
	mike.leach@linaro.org,
	marcan@marcan.st,
	maz@kernel.org,
	john.g.garry@oracle.com,
	james.clark@arm.com,
	irogers@google.com,
	will@kernel.org,
	tmricht@linux.ibm.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2] perf print-events: make is_event_supported() more robust
Date: Mon, 26 Feb 2024 08:20:24 -0800
Message-ID: <170896440860.1919080.16667714946535783711.b4-ty@kernel.org>
In-Reply-To: <20240126145605.1005472-1-mark.rutland@arm.com>
References: <20240126145605.1005472-1-mark.rutland@arm.com>
Precedence: bulk
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit

On Fri, 26 Jan 2024 14:56:05 +0000, Mark Rutland wrote:
> Currently the perf tool doesn't detect support for extended event types
> on Apple M1/M2 systems, and will not auto-expand plain PERF_EVENT_TYPE
> hardware events into per-PMU events. This is due to the detection of
> extended event types not handling mandatory filters required by the
> M1/M2 PMU driver.
> 
> PMU drivers and the core perf_events code can require that
> perf_event_attr::exclude_* filters are configured in a specific way and
> may reject certain configurations of filters, for example:
> 
> [...]

Applied to perf-tools-next, thanks!

Best regards,
-- 
Namhyung Kim <namhyung@kernel.org>