mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Zixin Wang <w1355457260@gmail.com>
Cc: linux-doc@vger.kernel.org, linux-rt-devel@lists.linux.dev,
	clrkwllms@kernel.org, rostedt@goodmis.org, corbet@lwn.net,
	frederic@kernel.org, wagi@monom.org, atomlin@atomlin.com,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] Documentation: real-time: Add boot parameters and task isolation section
Date: Fri, 20 Nov 2026 16:48:11 +0100	[thread overview]
Message-ID: <20261120154811.Svr3Wf_j@linutronix.de> (raw)
In-Reply-To: <20261120152836.100638-1-w1355457260@gmail.com>

On 2026-11-20 23:28:36 [+0800], Zixin Wang wrote:
> One open question about the idle state limits section: I could not
> exercise processor.max_cstate or intel_idle.max_cstate locally.  QEMU
> exposes no ACPI _CST states, so the kernel registers no cpuidle states,
> and intel_idle is not built for this AMD test host.  Should the section
> stay as documentation-only guidance, or would you prefer that I drop or
> rework it (for example, by pointing to
> Documentation/admin-guide/pm/cpuidle.rst)?  I am happy to adjust it.

processor.max_cstate should work on AMD unless it does not expose
certain things. But then it might be an embedded board, not having this?
Does cpupower report anything?
And I don't thing this is exposed on qemu since the guest goes only idle
and the host decides what to do.

The CONFIG_CPU_IDLE section already mentions processor.max_cstate=1 and
refers to cpupower among other points.

I don't know how you want to structure this information but parts of it
are already there. You could go on an add some settings for i915 for
instance. But then it feels like it should be within the DRM section
because it somehow belongs together.

And there is a CONFIG_NO_HZ/ CONFIG_NO_HZ_FULL section for instance.
It also says that the transition is a bit more expensive. This repeated
again later on.

Maybe it wouldn't be that bad if the config switches would have a
suggestion for the comandline argument that might be helpful/
considered. That way the information pieces stay together.

What do you think?

Sebastian

      reply	other threads:[~2026-11-20 15:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-20 15:28 Zixin Wang
2026-11-20 15:48 ` Sebastian Andrzej Siewior [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=20261120154811.Svr3Wf_j@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=atomlin@atomlin.com \
    --cc=clrkwllms@kernel.org \
    --cc=corbet@lwn.net \
    --cc=frederic@kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-devel@lists.linux.dev \
    --cc=rostedt@goodmis.org \
    --cc=w1355457260@gmail.com \
    --cc=wagi@monom.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

all inboxes | Powered by JetHome®