mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Yury Norov <ynorov@nvidia.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Yury Norov <yury.norov@gmail.com>,
	linux-kernel@vger.kernel.org
Cc: K Prateek Nayak <kprateek.nayak@amd.com>
Subject: Re: [PATCH] virt: steal_governor: store only the sampling delay
Date: Wed, 28 Oct 2026 14:34:49 +0530	[thread overview]
Message-ID: <3cddf9d4-6ce8-4633-97f4-17eb70136db5@linux.ibm.com> (raw)
In-Reply-To: <20261026171252.3860162-1-ynorov@nvidia.com>



On 10/26/26 10:42 PM, Yury Norov wrote:
> The governor stores the sampling interval in both milliseconds and
> jiffies, although delayed work only needs the latter.
> 
> Convert interval_ms to jiffies in the module parameter setter and store
> it directly in sg_ctx.delay. Initialize the default delay to HZ and
> remove the redundant interval_ms member and initialization conversion.
> 
> Keep the read-only interval_ms parameter by converting the delay back
> to milliseconds in its getter. Use the same conversion for the startup
> message. Both now report the effective interval after jiffy rounding.
> 
> Signed-off-by: Yury Norov <ynorov@nvidia.com>
> ---
>   drivers/virt/steal_governor.c | 18 +++++++++++-------
>   1 file changed, 11 insertions(+), 7 deletions(-)
> 
> diff --git a/drivers/virt/steal_governor.c b/drivers/virt/steal_governor.c
> index 6e31f9923dea..81e5089ba824 100644
> --- a/drivers/virt/steal_governor.c
> +++ b/drivers/virt/steal_governor.c
> @@ -39,14 +39,13 @@ struct steal_governor {
>   	ktime_t			time;
>   	u64			steal;
>   	unsigned long		delay;
> -	unsigned int		interval_ms;
>   	unsigned int		high_threshold;
>   	unsigned int		low_threshold;
>   	struct delayed_work	work;
>   };
>   
>   static struct steal_governor sg_ctx = {
> -	.interval_ms	=	1000,	/* 1 second */
> +	.delay		=	HZ,	/* 1 second */
>   	.high_threshold =	500,	/* 5% */
>   	.low_threshold	=	200,	/* 2% */
>   };
> @@ -74,15 +73,21 @@ static int param_set_interval_ms(const char *val, const struct kernel_param *kp)
>   		return -EINVAL;
>   	}
>   
> -	return param_set_uint(val, kp);
> +	*(unsigned long *)kp->arg = msecs_to_jiffies(interval);
> +	return 0;
> +}
> +
> +static int param_get_interval_ms(char *buffer, const struct kernel_param *kp)
> +{
> +	return sprintf(buffer, "%u\n", jiffies_to_msecs(*(unsigned long *)kp->arg));
>   }
>   
>   static const struct kernel_param_ops interval_ms_ops = {
>   	.set = param_set_interval_ms,
> -	.get = param_get_uint,
> +	.get = param_get_interval_ms,
>   };
>   
> -module_param_cb(interval_ms, &interval_ms_ops, &sg_ctx.interval_ms, 0444);
> +module_param_cb(interval_ms, &interval_ms_ops, &sg_ctx.delay, 0444);
>   MODULE_PARM_DESC(interval_ms,
>   		 "Sampling frequency in milliseconds. default: 1000");
>   
> @@ -270,13 +275,12 @@ static int __init steal_governor_init(void)
>   		return -EINVAL;
>   	}
>   
> -	sg_ctx.delay = msecs_to_jiffies(sg_ctx.interval_ms);
>   	INIT_DELAYED_WORK(&sg_ctx.work, steal_governor_loop);
>   	sg_ctx.steal = get_system_steal_time();
>   	sg_ctx.time = ktime_get();
>   	schedule_delayed_work(&sg_ctx.work, sg_ctx.delay);
>   	pr_info("enabled. interval: %ums, high_threshold: %u, low_threshold: %u\n",
> -		sg_ctx.interval_ms, sg_ctx.high_threshold, sg_ctx.low_threshold);
> +		jiffies_to_msecs(sg_ctx.delay), sg_ctx.high_threshold, sg_ctx.low_threshold);
>   
>   	return 0;
>   }

Looks good to me. One less variable.

Reviewed-by: Shrikanth Hegde <sshegde@linux.ibm.com>

      reply	other threads:[~2026-10-28  9:05 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-26 17:12 Yury Norov
2026-10-28  9:04 ` Shrikanth Hegde [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=3cddf9d4-6ce8-4633-97f4-17eb70136db5@linux.ibm.com \
    --to=sshegde@linux.ibm.com \
    --cc=kprateek.nayak@amd.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=ynorov@nvidia.com \
    --cc=yury.norov@gmail.com \
    /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®