[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <77ebe99f-9034-990e-533e-544d75e564b2@amd.com>
Date: Wed, 3 May 2023 14:02:52 +0530
From: Ravi Bangoria <ravi.bangoria@....com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: namhyung@...nel.org, eranian@...gle.com, acme@...nel.org,
mark.rutland@....com, jolsa@...nel.org, irogers@...gle.com,
bp@...en8.de, kan.liang@...ux.intel.com, adrian.hunter@...el.com,
maddy@...ux.ibm.com, x86@...nel.org,
linux-perf-users@...r.kernel.org, linux-kernel@...r.kernel.org,
sandipan.das@....com, ananth.narayan@....com,
santosh.shukla@....com, Ravi Bangoria <ravi.bangoria@....com>
Subject: Re: [PATCH v3 1/3] perf/core: Rework forwarding of {task|cpu}-clock
events
>> @@ -322,6 +322,9 @@ struct pmu {
>> /* number of address filters this PMU can do */
>> unsigned int nr_addr_filters;
>>
>> + /* Skip creating pmu device and sysfs interface. */
>> + bool skip_sysfs_dev;
>> +
>> /*
>> * Fully disable/enable this PMU, can be used to protect from the PMI
>> * as well as for lazy/batch writing of the MSRs.
>
> Does this make sense?
Yes! Will respin with this included.
Thanks,
Ravi
Powered by blists - more mailing lists