All the mail mirrored from lore.kernel.org
 help / color / mirror / Atom feed
From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: "John B. Wyatt IV" <jwyatt@redhat.com>
Cc: Miguel Miranda <mmikernel@gmail.com>,
	RT <linux-rt-users@vger.kernel.org>
Subject: Re: Seeking input on beginner-level bugs related to preempt_RT
Date: Mon, 29 Apr 2024 11:45:18 +0200	[thread overview]
Message-ID: <20240429094518.3SXHHssO@linutronix.de> (raw)
In-Reply-To: <ZiAJ60Ugb-1MaTkQ@thinkpad2021>

On 2024-04-17 13:42:03 [-0400], John B. Wyatt IV wrote:
> On Fri, Apr 12, 2024 at 05:00:39PM -0600, Miguel Miranda wrote:
> > Hello everyone,
> > 
> 
> Welcome.
Hi,

> > I am currently looking for beginner-level bugs related to preempt_RT for the
> > Linux kernel Bug Fixing Spring Unpaid 2024.
> 
> What is your experience level? Have you built and run an rt kernel
> before? (Selected Fully Preemptive in kconfig?)
> 
> > Although I am not an expert in
> > RT, I have been trying to identify some bugs and our mentors have suggested
> > using ring testers such as syzkaller and test frameworks like
> > kernelselftests to find and reproduce these bugs on our own.
> 
> A lot of the bugs we encounter are around locking. RT changes
> the way locks are handled in the kernel. That is one avenue I would
> encourage you to study.

I would suggest to build the PREEMPT_RT kernel and starting using on a
wide range of hardware and seeing how it behaves.

Sebastian

      reply	other threads:[~2024-04-29  9:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 23:00 Seeking input on beginner-level bugs related to preempt_RT Miguel Miranda
2024-04-17 17:42 ` John B. Wyatt IV
2024-04-29  9:45   ` 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=20240429094518.3SXHHssO@linutronix.de \
    --to=bigeasy@linutronix.de \
    --cc=jwyatt@redhat.com \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=mmikernel@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.