From: Daniel Bristot de Oliveira <bristot@kernel.org>
To: linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Cc: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Valentin Schneider" <valentin.schneider@arm.com>,
"Juri Lelli" <juri.lelli@redhat.com>,
"Dhaval Giani" <dhaval.giani@gmail.com>,
"Clark Williams" <williams@redhat.com>,
"Kate Stewart" <kstewart@linuxfoundation.org>,
"Kate Carcia" <kcarcia@redhat.com>,
"Phil Auld" <pauld@redhat.com>,
"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
"Joel Fernandes (Google)" <joel@joelfernandes.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Tom Zanussi" <tom.zanussi@linux.intel.com>,
"Luis Claudio R. Gonçalves" <lclaudio@redhat.com>,
"John Kacur" <jkacur@redhat.com>,
"Peter Zijlstra" <peterz@infradead.org>,
"Ingo Molnar" <mingo@redhat.com>,
"Vincent Guittot" <vincent.guittot@linaro.org>,
"Mark Brown" <broonie@kernel.org>,
"Dietmar Eggemann" <dietmar.eggemann@arm.com>,
"Daniel Wagner" <wagi@monom.org>
Subject: [ANNOUNCE] CFP: Real-Time Microconference - Linux Plumbers Conference 2021
Date: Fri, 23 Jul 2021 13:58:33 +0200 [thread overview]
Message-ID: <4c666746-a4bd-5111-1512-58d030987f8b@kernel.org> (raw)
The Real-time microconference focuses on finishing the last lap of getting the
PREEMPT_RT[1] patch set into mainline. Many of these missing pieces, however,
are not at the core of real-time features (like locking, and scheduling), but
instead, on other subsystems that compose the kernel, like file systems and
memory management. Making this Linux subsystems compatible with PREEMPT_RT
requires finding a solution that is acceptable by subsystem maintainer, without
having these subsystems suffer from performance or complexity issues.
Suggested Topics:
- New tools for PREEMPT_RT analysis [2].
- How do we teach the rest of the kernel developers how not to break
PREEMPT_RT?
- Stable maintainers tools discussion & improvements: [3]
- The usage of PREEMPT_RT on safety-critical systems: what do we need to do?
- Make NAPI and the kernel-rt working better together [5]
- Migrate disable and the problems that they cause on rt tasks [6]
- It is time to discuss the "BKL"-like style of our preempt/bh/irq_disable()
synchronization functions.
- How do we close the documentation gap
- The status of the merge, and how can we resolve the last issues that block
the merge
- Invite the developers of the areas where patches are still under discussion
to help to find an agreement
- How can we improve the testing of the -rt, to follow the problems raised as
Linus tree advances?
- What’s next?
If you are interested in participating in this microconference and have topics
to propose, please use the LPC CfP process, and select "Real-time MC" for the
"Track". More topics will be added based on CfP for LPC microconference.
MC leads:
- Daniel Bristot de Oliveira <bristot@redhat.com>
- Steven Rostedt <rostedt@goodmis.org>
- Clark Williams <williams@redhat.com>
- Dhaval Giani <dhaval.giani@oracle.com>
- Kate Stewart <stewart@linux.com>
Links:
[1] https://wiki.linuxfoundation.org/realtime/start
[2] https://github.com/bristot/rtsl/
[3] https://github.com/igaw/stable-rt-tools
[4] https://www.linux.com/news/in-the-trenches-with-thomas-gleixner-real-time-linux-kernel-patch-set/
[5] Discussions:
https://lore.kernel.org/netdev/20210514222402.295157-1-kuba@kernel.org/
https://lore.kernel.org/lkml/YJofplWBz8dT7xiw@localhost.localdomain/
[6] https://lore.kernel.org/linux-arm-kernel/20200924082717.GA1362448@hirez.programming.kicks-ass.net/T/
reply other threads:[~2021-07-23 12:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4c666746-a4bd-5111-1512-58d030987f8b@kernel.org \
--to=bristot@kernel.org \
--cc=acme@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=broonie@kernel.org \
--cc=dhaval.giani@gmail.com \
--cc=dietmar.eggemann@arm.com \
--cc=jkacur@redhat.com \
--cc=joel@joelfernandes.org \
--cc=juri.lelli@redhat.com \
--cc=kcarcia@redhat.com \
--cc=kstewart@linuxfoundation.org \
--cc=lclaudio@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=paulmck@linux.vnet.ibm.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=tom.zanussi@linux.intel.com \
--cc=valentin.schneider@arm.com \
--cc=vincent.guittot@linaro.org \
--cc=wagi@monom.org \
--cc=williams@redhat.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 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®