From: Shrikanth Hegde <sshegde@linux.ibm.com>
To: Robert Joslyn <robert_joslyn@selinc.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-rt-users@vger.kernel.org" <linux-rt-users@vger.kernel.org>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"rostedt@goodmis.org" <rostedt@goodmis.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Subject: Re: [PATCH] powerpc: Allow scheduling of IRQ with PREEMPT_RT
Date: Wed, 8 Jan 2025 10:26:36 +0530 [thread overview]
Message-ID: <e0364c9a-0364-4993-99a1-9e51a47529fe@linux.ibm.com> (raw)
In-Reply-To: <SJ2PR22MB3822B4550212A2418187A075E5112@SJ2PR22MB3822.namprd22.prod.outlook.com>
On 1/7/25 23:43, Robert Joslyn wrote:
>> -----Original Message-----
>> From: Shrikanth Hegde <sshegde@linux.ibm.com>
>> Sent: Tuesday, January 7, 2025 5:10 AM
>> To: Robert Joslyn <robert_joslyn@selinc.com>
>> Cc: linux-kernel@vger.kernel.org; linux-rt-users@vger.kernel.org;
>> tglx@linutronix.de; rostedt@goodmis.org; Sebastian Andrzej Siewior
>> <bigeasy@linutronix.de>
>> Subject: Re: [PATCH] powerpc: Allow scheduling of IRQ with PREEMPT_RT
>>
>> [Caution - External]
>>
>> On 1/7/25 17:26, Sebastian Andrzej Siewior wrote:
>>> On 2024-12-26 11:12:38 [-0800], Robert Joslyn wrote:
>>>> This branch is needed to allow preemptible IRQs to be scheduled,
>>>> otherwise the kernel hangs during boot on my e300 based platforms.
>>>> This branch is needed for both CONFIG_PREEMPT and
>> CONFIG_PREEMPT_RT,
>>
>> Hi Robert.
>>
>> Are you running with preempt=full or enabled preempt_rt ?
>> rt is yet to be supported on powerpc. are you having it enabled out of tree?
>
> I'm running PREEMPT_RT using the out of tree patches on 6.6.58-rt45:
> https://git.kernel.org/pub/scm/linux/kernel/git/rt/linux-stable-rt.git/
>
> I haven't tried using the mainline kernel, since as you said, it doesn't have powerpc support for PREEMPT_RT yet.
>
>>
>> Also, I have sent out patch to enable dynamic preemption. It uses
>> preempt_model_preemptible.
>> I think it should work for you as well. If you could give that a try and ensure it
>> works, it would be great.
>> https://urldefense.com/v3/__https://lore.kernel.org/all/20250106051919.5
>> 5020-2-
>> sshegde@linux.ibm.com/__;!!O7uE89YCNVw!IDeomstGeuiEZi9FmLHH8C2xo
>> PPo_ewL-
>> k2kiQ9CmVID35U4J_v3Dkafjo3RnS9ygPoUZWwyyp91SP2euRkKArk$
>
> Does the dynamic preemption support let me enable the same functionality as PREEMPT_RT with the out of tree patches? I can test it out either way.
>
with preempt_rt, dynamic preemption allows you to switch between full
and lazy. without preempt_rt, you can switch between none,
voluntary,full and lazy.
> Thanks,
> Robert
prev parent reply other threads:[~2025-01-08 4:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-26 19:12 Robert Joslyn
2025-01-07 11:56 ` Sebastian Andrzej Siewior
2025-01-07 11:58 ` Sebastian Andrzej Siewior
2025-01-07 18:09 ` Robert Joslyn
2025-01-09 11:44 ` Sebastian Andrzej Siewior
2025-01-10 22:36 ` Robert Joslyn
2025-01-07 13:10 ` Shrikanth Hegde
2025-01-07 18:13 ` Robert Joslyn
2025-01-08 4:56 ` 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=e0364c9a-0364-4993-99a1-9e51a47529fe@linux.ibm.com \
--to=sshegde@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=robert_joslyn@selinc.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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®