From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: 余华兵 <yhb@ruijie.com.cn>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"peterz@infradead.org" <peterz@infradead.org>
Subject: Re: sched: Clarify PREEMPT is full preemption model
Date: Thu, 16 Jan 2025 14:07:51 +0530 [thread overview]
Message-ID: <7ce44659-60a6-4647-bb74-fb6017ceb129@linux.ibm.com> (raw)
In-Reply-To: <cb013939c11991f429773b83a6ff1513221dd678.a11e9ded.5679.4468.8cc8.fe30e9b90f3f@feishu.cn>
Please use plaintext for sending mail containing patches.
Not able to see the patch on my mail client. Also the text is not formatted.
https://docs.kernel.org/process/submitting-patches.html#no-mime-no-links-no-compression-no-attachments-just-plain-text
On 1/15/25 15:24, 余华兵 wrote:
> The configuration file "kernel/Kconfig. preempt" says that PREEMPT_RT is
> fully preemptible, but from the function preempt_model_full() it can be
> seen that PREEMPT is full preemption model. --------------------------
> kernel/Kconfig.preempt config PREEMPT bool "Preemptible Kernel
> (Low-Latency Desktop)" config PREEMPT_RT bool "Fully Preemptible
> Kernel (Real-Time)" include/linux/preempt.h static inline bool
> preempt_model_full(void) { return IS_ENABLED(CONFIG_PREEMPT); }
> --------------------------
On Preempt_RT kernel, the spinlocks are sleeping locks and irqs can run as threaded.
So even those can be preempted if necessary. That is not true with preempt=full alone.
I suggest that the configuration file
> "kernel/Kconfig. preempt" should be consistent with the function
> preempt_model_full(). Modify the file "kernel/Kconfig.preempt" as
> follows. ------------------ config PREEMPT bool "Fully
> Preemptible Kernel (Low-Latency Desktop)" config PREEMPT_RT bool
> "Real-time Kernel" ------------------
prev parent reply other threads:[~2025-01-16 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-15 9:54 余华兵
2025-01-16 8:37 ` 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=7ce44659-60a6-4647-bb74-fb6017ceb129@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=yhb@ruijie.com.cn \
/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®