From: Jason Andryuk <jason.andryuk@amd.com>
To: Roger Pau Monne <roger.pau@citrix.com>, <xen-devel@lists.xenproject.org>
Cc: Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH 2/2] xen/cpufreq: fix usages of align_timer() in the on-demand governor
Date: Mon, 15 Jun 2026 13:44:54 -0400 [thread overview]
Message-ID: <d00f8d01-33c2-4b43-9ca5-c7aa98488ff2@amd.com> (raw)
In-Reply-To: <20260227073259.1200-3-roger.pau@citrix.com>
On 2026-02-27 02:32, Roger Pau Monne wrote:
> The first parameter passed to align_timer() is the timer expiration, not
> the current time. Adjust the calls to align_timer() in the on-demand
> governor to pass the expected timer expiration as the first parameter.
Internally, we have a report of a benchmark regressing ~6% with this
change on 4.20.
s_time_t align_timer(s_time_t firsttick, uint64_t period)
{
if ( !period )
return firsttick;
return firsttick + (period - 1) - ((firsttick - 1) % period);
}
The code rounds firsttick up to the next period:
align_timer(0, period) -> 0
align_timer(1, period) -> period
align_timer(period - 1, period) -> period
align_timer(period, period) -> period
align_timer(period + 1, period) -> 2 * period
With the change of this patch adding the period before calling
align_timer(), the timer is set for two periods in the future. The only
exception is when firsttick % period == 0. I think that is unlikely to
happen since NOW() will always be a little after the period. Even if it
did happen, the timer would fire immediately, but the next timer would
be set for 1 period later.
So I think we want to revert?
Regards,
Jason
>
> Fixes: af74e3a15a83 ("cpufreq: align dbs timer for better package C state residency")
> Fixes: 382b95f627a9 ("Fix cpufreq HW-ALL coordination handle")
> Signed-off-by: Roger Pau Monné <roger.pau@citrix.com>
> ---
> xen/drivers/cpufreq/cpufreq_ondemand.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/xen/drivers/cpufreq/cpufreq_ondemand.c b/xen/drivers/cpufreq/cpufreq_ondemand.c
> index 537695eaab19..0d94c0e464a6 100644
> --- a/xen/drivers/cpufreq/cpufreq_ondemand.c
> +++ b/xen/drivers/cpufreq/cpufreq_ondemand.c
> @@ -185,7 +185,8 @@ static void cf_check do_dbs_timer(void *dbs)
> dbs_check_cpu(dbs_info);
>
> set_timer(&per_cpu(dbs_timer, dbs_info->cpu),
> - align_timer(NOW() , dbs_tuners_ins.sampling_rate));
> + align_timer(NOW() + dbs_tuners_ins.sampling_rate,
> + dbs_tuners_ins.sampling_rate));
> }
>
> static void dbs_timer_init(struct cpu_dbs_info_s *dbs_info)
> @@ -400,6 +401,6 @@ void cpufreq_dbs_timer_resume(void)
> (void)cmpxchg(stoppable, -1, 1);
> }
> else
> - set_timer(t, align_timer(now, dbs_tuners_ins.sampling_rate));
> + set_timer(t, align_timer(t->expires, dbs_tuners_ins.sampling_rate));
> }
> }
next prev parent reply other threads:[~2026-06-15 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-27 7:32 [PATCH 0/2] xen/cpufreq: a couple of fixes for the sampling window Roger Pau Monne
2026-02-27 7:32 ` [PATCH 1/2] xen/cpufreq: fix adjusting of sampling window on early exit Roger Pau Monne
2026-03-02 9:46 ` Jan Beulich
2026-02-27 7:32 ` [PATCH 2/2] xen/cpufreq: fix usages of align_timer() in the on-demand governor Roger Pau Monne
2026-03-02 9:57 ` Jan Beulich
2026-06-15 17:44 ` Jason Andryuk [this message]
2026-06-15 18:33 ` Roger Pau Monné
2026-06-15 19:31 ` Jason Andryuk
2026-06-15 19:22 ` Roger Pau Monné
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=d00f8d01-33c2-4b43-9ca5-c7aa98488ff2@amd.com \
--to=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.