From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 6E7D027EFE7; Tue, 26 Aug 2025 13:28:52 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756214934; cv=none; b=Eq05NagswARJ/6sLzLNceOxuzMY6pCVlYwIkOGnmkl8qCS8N4oNsewtsLWuG5Tbj4NrIxPwv2cRJSEwb1N7XBL6Y3i112y+X5whfH0I9C/vDWiqaUkkfRJnDt9ksmCu/DuN4rAgJcTCqTuYaNifC3OLAIQQXs0S/0KtFyvzDU/8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1756214934; c=relaxed/simple; bh=pGd2Z5xxI8xMWlXX7wv1c9fIzDDiogCatnymFQsEKDM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=niqLBgUqo29AHg8mTqOAyhMMOAJ5lXtq0zqTJUiybUt3XF8SBLj/2wpqGNmhAl+iWQ3dAxEGPi4TPyYxBoWHbAskKgqpOc4Iis+jlLb9KGjGVCsJDKf4CehfsId7ggoo9MB3xDJTwdjDKQ1p028Sw1mrytnLnn8iCggrdwMcY0Q= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 742EB1A25; Tue, 26 Aug 2025 06:28:43 -0700 (PDT) Received: from J2N7QTR9R3 (usa-sjc-imap-foss1.foss.arm.com [10.121.207.14]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A56233F63F; Tue, 26 Aug 2025 06:28:45 -0700 (PDT) Date: Tue, 26 Aug 2025 14:28:43 +0100 From: Mark Rutland To: Peter Zijlstra Cc: Robin Murphy , mingo@redhat.com, will@kernel.org, acme@kernel.org, namhyung@kernel.org, alexander.shishkin@linux.intel.com, jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com, kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org, linux-alpha@vger.kernel.org, linux-snps-arc@lists.infradead.org, linux-arm-kernel@lists.infradead.org, imx@lists.linux.dev, linux-csky@vger.kernel.org, loongarch@lists.linux.dev, linux-mips@vger.kernel.org, linuxppc-dev@lists.ozlabs.org, linux-s390@vger.kernel.org, linux-sh@vger.kernel.org, sparclinux@vger.kernel.org, linux-pm@vger.kernel.org, linux-rockchip@lists.infradead.org, dmaengine@vger.kernel.org, linux-fpga@vger.kernel.org, amd-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org, coresight@lists.linaro.org, iommu@lists.linux.dev, linux-amlogic@lists.infradead.org, linux-cxl@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-riscv@lists.infradead.org Subject: Re: [PATCH 16/19] perf: Introduce positive capability for sampling Message-ID: References: <20250826130806.GY4067720@noisy.programming.kicks-ass.net> Precedence: bulk X-Mailing-List: linux-s390@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20250826130806.GY4067720@noisy.programming.kicks-ass.net> On Tue, Aug 26, 2025 at 03:08:06PM +0200, Peter Zijlstra wrote: > On Wed, Aug 13, 2025 at 06:01:08PM +0100, Robin Murphy wrote: > > Sampling is inherently a feature for CPU PMUs, given that the thing > > to be sampled is a CPU context. These days, we have many more > > uncore/system PMUs than CPU PMUs, so it no longer makes much sense to > > assume sampling support by default and force the ever-growing majority > > of drivers to opt out of it (or erroneously fail to). Instead, let's > > introduce a positive opt-in capability that's more obvious and easier to > > maintain. > > > diff --git a/include/linux/perf_event.h b/include/linux/perf_event.h > > index 4d439c24c901..bf2cfbeabba2 100644 > > --- a/include/linux/perf_event.h > > +++ b/include/linux/perf_event.h > > @@ -294,7 +294,7 @@ struct perf_event_pmu_context; > > /** > > * pmu::capabilities flags > > */ > > -#define PERF_PMU_CAP_NO_INTERRUPT 0x0001 > > +#define PERF_PMU_CAP_SAMPLING 0x0001 > > #define PERF_PMU_CAP_NO_NMI 0x0002 > > #define PERF_PMU_CAP_AUX_NO_SG 0x0004 > > #define PERF_PMU_CAP_EXTENDED_REGS 0x0008 > > @@ -305,6 +305,7 @@ struct perf_event_pmu_context; > > #define PERF_PMU_CAP_EXTENDED_HW_TYPE 0x0100 > > #define PERF_PMU_CAP_AUX_PAUSE 0x0200 > > #define PERF_PMU_CAP_AUX_PREFER_LARGE 0x0400 > > +#define PERF_PMU_CAP_NO_INTERRUPT 0x0800 > > So NO_INTERRUPT was supposed to be the negative of your new SAMPLING > (and I agree with your reasoning). > > What I'm confused/curious about is why we retain NO_INTERRUPT? I see from your other reply that you spotted the next patch does that. For the sake of other reviewers or anyone digging through the git history it's probably worth adding a line to this commit message to say: | A subsequent patch will remove PERF_PMU_CAP_NO_INTERRUPT as this | requires some additional cleanup. Mark.