From: Michael Schmitz <schmitzmic@gmail.com>
To: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Jean-Michel Hautbois <jeanmichel.hautbois@yoseli.org>
Cc: linux-m68k@lists.linux-m68k.org
Subject: Re: PREEMPT_RT support
Date: Tue, 1 Oct 2024 15:24:11 +1300 [thread overview]
Message-ID: <a67fb246-4902-1b82-44cb-029f20fc36fe@gmail.com> (raw)
In-Reply-To: <0bd77991e6223c4cec065ac6f7a348f9ea8e6c2a.camel@physik.fu-berlin.de>
Hi Adrian,
Am 30.09.2024 um 21:38 schrieb John Paul Adrian Glaubitz:
> Hello Jean-Michel,
>
> On Mon, 2024-09-30 at 10:19 +0200, Jean-Michel Hautbois wrote:
>> I wanted to try PREEMPT_RT. I added the support for it:
>> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
>> index c7880f375518..b0360167574d 100644
>> --- a/arch/m68k/Kconfig
>> +++ b/arch/m68k/Kconfig
>> @@ -39,6 +39,7 @@ config M68K
>> select OLD_SIGSUSPEND3
>> select UACCESS_MEMCPY if !MMU
>> select ZONE_DMA
>> + select ARCH_SUPPORTS_RT
>>
>> config CPU_BIG_ENDIAN
>> def_bool y
>>
>> And set PREEMPT_RT then it fails to boot:
>> [ 6.517000] BUG: scheduling while atomic: init/1/0x00010001
>> (...)
>> Any idea, thoughts :-) ?
>
> From what I know an architecture has to be explicitly ported to support
> a realtime kernel. Simply enabling the feature therefore won't work.
Making sure softirqs are run from a separate kernel thread and not from
atomic context would be a good start. Adding preempt_disable() /
preempt_enable() around more critcal sections may be needed as well.
Git history of those architectures that support PREEMPT_RT might be
informative.
Cheers,
Michael
>
> Adrian
>
prev parent reply other threads:[~2024-10-01 2:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-30 8:19 PREEMPT_RT support Jean-Michel Hautbois
2024-09-30 8:38 ` John Paul Adrian Glaubitz
2024-10-01 2:24 ` Michael Schmitz [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=a67fb246-4902-1b82-44cb-029f20fc36fe@gmail.com \
--to=schmitzmic@gmail.com \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jeanmichel.hautbois@yoseli.org \
--cc=linux-m68k@lists.linux-m68k.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;
as well as URLs for NNTP newsgroup(s).