public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Aaron Tomlin <atomlin@atomlin.com>
To: gregkh@linuxfoundation.org, rafael@kernel.org, dakr@kernel.org
Cc: riel@surriel.com, frederic@kernel.org, atomlin@atomlin.com,
	linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/1] tick/nohz: avoid showing '(null)' if nohz_full= not set
Date: Mon,  6 Oct 2025 21:25:03 -0400	[thread overview]
Message-ID: <20251007012504.16118-1-atomlin@atomlin.com> (raw)

In the context of CONFIG_NO_HZ_FULL=y, tick_nohz_full_mask (of type
cpumask_var_t) is initialised to 0. Memory is only allocated to the cpumask
data structure, when Linux kernel boot-time parameter "nohz_full=" is
correctly specified (see tick_nohz_full_setup() and housekeeping_setup()).
If "nohz_full=" is not set and an attempt is made to read
/sys/devices/system/cpu/nohz_full, '(null)' can be displayed:

    ❯ cat /sys/devices/system/cpu/nohz_full
    (null)

This patch changes the output to print a newline (or 0x0A) instead of
'(null)', making it consistent with print_cpus_isolated() behaviour.


Changes since v1 [1]:

 - Refactor to use an if statement (Greg KH)

[1]: https://lore.kernel.org/lkml/20251006005824.76187-1-atomlin@atomlin.com/

Aaron Tomlin (1):
  tick/nohz: avoid showing '(null)' if nohz_full= not set

 drivers/base/cpu.c | 6 +++++-
 1 file changed, 5 insertions(+), 1 deletion(-)

-- 
2.49.0


             reply	other threads:[~2025-10-07  1:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-07  1:25 Aaron Tomlin [this message]
2025-10-07  1:25 ` [PATCH v2 1/1] tick/nohz: avoid showing '(null)' if nohz_full= not set Aaron Tomlin
2025-10-10  3:28   ` Nathan Chancellor

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=20251007012504.16118-1-atomlin@atomlin.com \
    --to=atomlin@atomlin.com \
    --cc=dakr@kernel.org \
    --cc=frederic@kernel.org \
    --cc=gregkh@linuxfoundation.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