From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT
Date: Wed, 14 Oct 2015 01:04:01 +0200 [thread overview]
Message-ID: <1747675.QSGVOD93O5@vostro.rjw.lan> (raw)
In-Reply-To: <20151013221941.GF14464@wotan.suse.de>
On Wednesday, October 14, 2015 12:19:41 AM Luis R. Rodriguez wrote:
> On Wed, Oct 14, 2015 at 12:40:10AM +0200, Rafael J. Wysocki wrote:
> > On Tuesday, October 13, 2015 12:42:30 PM Steven Rostedt wrote:
> > >
> > > Now that it was announced in Dublin last week that mainlining
> > > PREEMPT_RT has funding, I would like to propose a tech topic to discuss
> > > what is needed to be done in the near future.
> > >
> > > Thomas Gleixner and his minions will be doing the brunt of the work,
> > > but there's issues that need to be addressed with the rest of the
> > > kernel. The various topics would include:
> > >
> > > CPU hotplug
> > > preempt_disable and local_irq_disable annotations
> > > new timer_wheel implementation
> > > simple waitqueues
> > > trylock boosting
> > >
> > > Several of the Real Time developers will be present at kernel summit. I
> > > think this would be a great opportunity to have them be able to sit
> > > down together and discuss the remaining issues.
> >
> > Well, that's not limited to the RT developers even.
> >
> > Good topic.
>
> How much of this is the above topics Vs lack of good semantics in general, or
> code which needs love / good design? I ask as we have a few 'semantic'
> discussions, and I have a feeling there might be overlap.
At this time it is not particularly clear to me how much overlap there's going
to be, if any.
And if there is overlap, we should be able to notice that and avoid
discussing the same thing twice, perhaps?
Thanks,
Rafael
next prev parent reply other threads:[~2015-10-13 22:35 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-13 16:42 Steven Rostedt
2015-10-13 17:33 ` Josh Triplett
2015-10-13 22:40 ` Rafael J. Wysocki
2015-10-13 22:19 ` Luis R. Rodriguez
2015-10-13 22:39 ` Steven Rostedt
2015-10-13 22:48 ` Luis R. Rodriguez
2015-10-13 23:04 ` Rafael J. Wysocki [this message]
2015-10-13 22:41 ` Luis R. Rodriguez
2015-10-14 7:35 ` Linus Walleij
2015-10-14 11:45 ` Christoph Lameter
2015-10-14 13:20 ` Steven Rostedt
2015-10-14 14:49 ` Christoph Lameter
2015-10-14 15:22 ` Steven Rostedt
2015-10-14 18:12 ` Christoph Lameter
2015-10-14 18:32 ` Steven Rostedt
2015-10-14 18:56 ` Christoph Lameter
2015-10-14 19:17 ` James Bottomley
2015-10-14 19:30 ` Tim Bird
2015-10-15 2:20 ` Steven Rostedt
2015-10-15 9:05 ` Thomas Gleixner
2015-10-14 20:24 ` Thomas Gleixner
2015-10-15 14:22 ` Christoph Lameter
2015-10-15 15:13 ` Steven Rostedt
2015-10-15 17:21 ` Jan Kara
2015-10-15 18:09 ` Steven Rostedt
2015-10-15 20:21 ` Thomas Gleixner
2015-10-15 20:37 ` Thomas Gleixner
2016-08-05 22:32 ` Darren Hart
2016-08-05 22:40 ` Darren Hart
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=1747675.QSGVOD93O5@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ksummit-discuss@lists.linuxfoundation.org \
--cc=mcgrof@suse.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