public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Yajun Deng" <yajun.deng@linux.dev>
To: "Namhyung Kim" <namhyung@kernel.org>
Cc: "Peter Zijlstra" <peterz@infradead.org>,
	"Ingo Molnar" <mingo@redhat.com>,
	"Arnaldo Carvalho de Melo" <acme@kernel.org>,
	"Mark Rutland" <mark.rutland@arm.com>,
	"Alexander Shishkin" <alexander.shishkin@linux.intel.com>,
	"Jiri Olsa" <jolsa@kernel.org>,
	"Stephane Eranian" <eranian@google.com>,
	"linux-perf-users" <linux-perf-users@vger.kernel.org>,
	"linux-kernel" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] perf/core: fix perf_event_mux_interval_ms when set zero
Date: Wed, 15 Jun 2022 01:29:55 +0000	[thread overview]
Message-ID: <f1cdd17717cef7ec33af096e104db03c@linux.dev> (raw)
In-Reply-To: <CAM9d7cj4=3DNz=kKhVbx0uKYwbbaQF6ZdjkezKPdT67j8rcEMg@mail.gmail.com>

June 15, 2022 6:08 AM, "Namhyung Kim" <namhyung@kernel.org> wrote:

> Hello,
> 
> On Tue, Jun 14, 2022 at 3:38 AM Yajun Deng <yajun.deng@linux.dev> wrote:
> 
>> The perf_event_mux_interval_ms is set to zero or one by default.
> 
> I see that __perf_mux_hrtimer_init() sets it to PERF_CPU_HRTIMER
> if it's less than 1.
> 
Yes, pmu->hrtimer_interval_ms was set to PERF_CPU_HRTIMER, but perf_event_mux_interval_ms didn't.
We can execute 'cat /sys/devices/intel_pt/perf_event_mux_interval_ms' see that.

> Thanks,
> Namhyung
> 
>> It can't change back when someone changes it from zero to another
>> value.
>> 
>> Make perf_event_mux_interval_ms to PERF_CPU_HRTIMER when set zero.
>> 
>> Fixes: 62b856397927 ("perf: Add sysfs entry to adjust multiplexing interval per PMU")
>> Signed-off-by: Yajun Deng <yajun.deng@linux.dev>
>> ---
>> kernel/events/core.c | 5 ++++-
>> 1 file changed, 4 insertions(+), 1 deletion(-)
>> 
>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>> index 61ad10862c21..73c8c7462bbf 100644
>> --- a/kernel/events/core.c
>> +++ b/kernel/events/core.c
>> @@ -10954,9 +10954,12 @@ perf_event_mux_interval_ms_store(struct device *dev,
>> if (ret)
>> return ret;
>> 
>> - if (timer < 1)
>> + if (timer < 0)
>> return -EINVAL;
>> 
>> + if (timer < 1)
>> + timer = PERF_CPU_HRTIMER;
>> +
>> /* same value, noting to do */
>> if (timer == pmu->hrtimer_interval_ms)
>> return count;
>> --
>> 2.25.1

      reply	other threads:[~2022-06-15  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-14 10:37 [PATCH] perf/core: fix perf_event_mux_interval_ms when set zero Yajun Deng
2022-06-14 22:08 ` Namhyung Kim
2022-06-15  1:29   ` Yajun Deng [this message]

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=f1cdd17717cef7ec33af096e104db03c@linux.dev \
    --to=yajun.deng@linux.dev \
    --cc=acme@kernel.org \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=eranian@google.com \
    --cc=jolsa@kernel.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 \
    /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