From: Mark Barnett <mark.barnett@arm.com>
To: Leo Yan <leo.yan@arm.com>
Cc: peterz@infradead.org, mingo@redhat.com, acme@kernel.org,
namhyung@kernel.org, irogers@google.com, ben.gainey@arm.com,
deepak.surti@arm.com, ak@linux.intel.com, will@kernel.org,
james.clark@arm.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, jolsa@kernel.org,
adrian.hunter@intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/5] perf: Allow periodic events to alternate between two sample periods
Date: Fri, 7 Mar 2025 20:28:13 +0000 [thread overview]
Message-ID: <c62a9f8a-312d-4f9e-9022-265e53564101@arm.com> (raw)
In-Reply-To: <20250121130154.GA416913@e132581.arm.com>
On 1/21/25 13:01, Leo Yan wrote:
>> local64_set(&hwc->period_left, hwc->sample_period);
>>
>> + if (attr->alt_sample_period) {
>> + hwc->sample_period = attr->alt_sample_period;
>> + hwc->using_alt_sample_period = true;
>> + }
>
> My understanding it sets a short sample window for the first period.
> Would it initialize the `hwc->period_left` with the updated sample
> period?
>
It sets the long period first: hwc->period_left is used to program the
PMU when setting up the event, and hwc->sample_period is queued up as
the next period to switch to.
>> +
>> + /*
>> + * alt_sample_period cannot be used with freq
>> + */
>> + if (attr->freq && attr->alt_sample_period)
>> + goto err_ns;
>> +
>
> It is good to validate parameters first. So move the checking before
> the adjustment for the alt sample period.
>
Ack. Done.
>> /*
>> * We do not support PERF_SAMPLE_READ on inherited events unless
>> * PERF_SAMPLE_TID is also selected, which allows inherited events to
>> @@ -12763,9 +12788,19 @@ SYSCALL_DEFINE5(perf_event_open,
>> if (attr.freq) {
>> if (attr.sample_freq > sysctl_perf_event_sample_rate)
>> return -EINVAL;
>> + if (attr.alt_sample_period)
>> + return -EINVAL;
>> } else {
>> if (attr.sample_period & (1ULL << 63))
>> return -EINVAL;
>> + if (attr.alt_sample_period) {
>> + if (!attr.sample_period)
>> + return -EINVAL;
>> + if (attr.alt_sample_period & (1ULL << 63))
>> + return -EINVAL;
>> + if (attr.alt_sample_period == attr.sample_period)
>> + attr.alt_sample_period = 0;
>
> In theory, the attr.alt_sample_period should be less than
> attr.sample_period, right?
>
Added some validation for this.
next prev parent reply other threads:[~2025-03-07 20:28 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-06 12:01 [PATCH v2 0/5] A mechanism for efficient support for per-function metrics mark.barnett
2025-01-06 12:01 ` [PATCH v2 1/5] perf: Allow periodic events to alternate between two sample periods mark.barnett
2025-01-21 13:01 ` Leo Yan
2025-03-07 20:28 ` Mark Barnett [this message]
2025-03-10 10:55 ` Leo Yan
2025-01-31 18:44 ` Rob Herring
2025-02-07 19:18 ` Mark Barnett
2025-01-06 12:01 ` [PATCH v2 2/5] perf: Allow adding fixed random jitter to the alternate sampling period mark.barnett
2025-01-06 12:01 ` [PATCH v2 3/5] tools/perf: Modify event parser to support alt-period term mark.barnett
2025-01-06 12:01 ` [PATCH v2 4/5] tools/perf: Modify event parser to support alt-period-jitter term mark.barnett
2025-01-06 12:01 ` [PATCH v2 5/5] perf: Record sample last_period before updating mark.barnett
2025-01-21 17:22 ` Leo Yan
2025-01-22 5:03 ` kernel test robot
2025-01-22 16:47 ` [PATCH v2 0/5] A mechanism for efficient support for per-function metrics James Clark
2025-02-07 19:23 ` Mark Barnett
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=c62a9f8a-312d-4f9e-9022-265e53564101@arm.com \
--to=mark.barnett@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=ak@linux.intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=ben.gainey@arm.com \
--cc=deepak.surti@arm.com \
--cc=irogers@google.com \
--cc=james.clark@arm.com \
--cc=jolsa@kernel.org \
--cc=leo.yan@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=will@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®