public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Aaron Tomlin <atomlin@atomlin.com>
Cc: rafael@kernel.org, dakr@kernel.org, riel@surriel.com,
	frederic@kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] tick/nohz: Expose housekeeping CPUs in sysfs
Date: Mon, 6 Oct 2025 08:33:57 +0200	[thread overview]
Message-ID: <2025100652-scolding-tractor-8745@gregkh> (raw)
In-Reply-To: <20251006005853.76335-1-atomlin@atomlin.com>

On Sun, Oct 05, 2025 at 08:58:53PM -0400, Aaron Tomlin wrote:
> Expose the current system-defined list of housekeeping CPUs in a new
> sysfs file: /sys/devices/system/cpu/housekeeping.

But you did not document that new file in Documentation/ABI so it's a
bit hard to review if this is really correct or not.

> This provides userspace performance tuning tools and resource managers
> with a canonical, reliable method to accurately identify the cores
> responsible for essential kernel maintenance workloads (RCU, timer
> callbacks, and unbound workqueues). Currently, tooling must manually
> calculate the housekeeping set by parsing complex kernel boot parameters
> (like isolcpus= and nohz_full=) and system topology, which is prone to
> error. This dedicated file simplifies the configuration of low-latency
> workloads.
> 
> Signed-off-by: Aaron Tomlin <atomlin@atomlin.com>
> ---
>  drivers/base/cpu.c | 14 ++++++++++++++
>  1 file changed, 14 insertions(+)
> 
> diff --git a/drivers/base/cpu.c b/drivers/base/cpu.c
> index f694b4b24d6c..c6511658f6cd 100644
> --- a/drivers/base/cpu.c
> +++ b/drivers/base/cpu.c
> @@ -300,6 +300,19 @@ static ssize_t print_cpus_isolated(struct device *dev,
>  }
>  static DEVICE_ATTR(isolated, 0444, print_cpus_isolated, NULL);
>  
> +static ssize_t print_cpus_hk(struct device *dev,
> +			     struct device_attribute *attr, char *buf)
> +{
> +	const struct cpumask *hk_mask;
> +
> +	hk_mask = housekeeping_cpumask(HK_TYPE_KERNEL_NOISE);
> +
> +	return housekeeping_enabled(HK_TYPE_KERNEL_NOISE) ?
> +		sysfs_emit(buf, "%*pbl\n", cpumask_pr_args(hk_mask)) :
> +		sysfs_emit(buf, "\n");

Please write out if statements, it makes it easier over time to
maintain.

> +static DEVICE_ATTR(housekeeping, 0444, print_cpus_hk, NULL);

DEVICE_ATTR_RO()?

thanks,

greg k-h

      reply	other threads:[~2025-10-06  6:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-06  0:58 [PATCH] tick/nohz: Expose housekeeping CPUs in sysfs Aaron Tomlin
2025-10-06  6:33 ` Greg KH [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=2025100652-scolding-tractor-8745@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=atomlin@atomlin.com \
    --cc=dakr@kernel.org \
    --cc=frederic@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=riel@surriel.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