ksummit.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@infradead.org>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TECH TOPIC] Mainlining PREEMPT_RT
Date: Fri, 5 Aug 2016 15:40:04 -0700	[thread overview]
Message-ID: <20160805224004.GB4952@f23x64.localdomain> (raw)
In-Reply-To: <20160805223238.GA4952@f23x64.localdomain>

On Fri, Aug 05, 2016 at 03:32:38PM -0700, Darren Hart wrote:
> On Tue, Oct 13, 2015 at 12:42:30PM -0400, 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.
> 
> I'm very interested in participating in this.
> 
> Is this a TECH topic or a CORE topic?

Apologies, this was from 2015. I failed to recognize that when searching for a
PREEMPT_RT TECH TOPIC proposal before responding to Davidlohr's self nomination
suggesting this topic.

Shall we recycle this topic for 2016 as well?

-- 
Darren Hart
Intel Open Source Technology Center

      reply	other threads:[~2016-08-05 22:40 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
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 [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=20160805224004.GB4952@f23x64.localdomain \
    --to=dvhart@infradead.org \
    --cc=ksummit-discuss@lists.linuxfoundation.org \
    --cc=rostedt@goodmis.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