mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mike Galbraith <umgwanakikbuti@gmail.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Juerg Haefliger <juergh@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-rt-users <linux-rt-users@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Carsten Emde <C.Emde@osadl.org>, John Kacur <jkacur@redhat.com>,
	Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
	Clark Williams <williams@redhat.com>
Subject: Re: [ANNOUNCE] 3.14.23-rt20
Date: Wed, 05 Nov 2014 16:44:19 +0100	[thread overview]
Message-ID: <1415202259.5402.90.camel@marge.simpson.net> (raw)
In-Reply-To: <20141105100056.152fd532@gandalf.local.home>

On Wed, 2014-11-05 at 10:00 -0500, Steven Rostedt wrote: 
> On Wed, 5 Nov 2014 15:43:24 +0100
> Juerg Haefliger <juergh@gmail.com> wrote:
> 
> > Thanks for the explanation. So is this considered a temporary failure
> > until multiple readers are allowed or does cpufreq need fixing or
> > something else? Just trying to figure out what to do next.
> 
> Good question. Unfortunately I don't know the answer to that.

[RFC PATCH RT] rwsem: The return of multi-reader PI rwsems

The above springs to mind.

-Mike


  parent reply	other threads:[~2014-11-05 15:44 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-31 21:03 Steven Rostedt
2014-11-02  7:30 ` Mike Galbraith
     [not found]   ` <CADLDEKvFvw7Aa98tVtM3z5JV8oocKqAdV4PqOMoZH2mXZ6x2jg@mail.gmail.com>
2014-11-05 14:04     ` Juerg Haefliger
2014-11-05 14:27     ` Steven Rostedt
2014-11-05 14:43       ` Juerg Haefliger
2014-11-05 15:00         ` Steven Rostedt
2014-11-05 15:35           ` Harry van Haaren
2014-11-05 15:44           ` Mike Galbraith [this message]
2014-11-05 16:07             ` Thomas Gleixner
2014-11-05 16:07       ` Thomas Gleixner
2014-11-05 22:29         ` Thomas Gleixner
2014-11-05 22:48           ` Steven Rostedt
2014-11-05 23:11             ` Thomas Gleixner
     [not found] ` <1414910967.5380.81.camel@marge.simpson.net>
2014-11-02  7:30   ` 3.14.23-rt20 - sched/numa: Fix task_numa_free() lockdep splat Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - wwmutex: fix __ww_mutex_lock_interruptible lockdep annotation Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - mm,memcg: make refill_stock()/consume_stock() use get_cpu_light() Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - fs,btrfs: fix rt deadlock on extent_buffer->lock Mike Galbraith
2015-02-17 11:56     ` Sebastian Andrzej Siewior
2015-02-17 12:23       ` Mike Galbraith
2015-02-18 10:47       ` Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - aio: fix rcu garbage collection might_sleep() splat Mike Galbraith
2015-02-17 12:53     ` Sebastian Andrzej Siewior
2015-02-17 14:01       ` Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - x86, UV: raw_spinlock conversion Mike Galbraith
2015-02-17 13:02     ` Sebastian Andrzej Siewior
2015-02-17 14:11       ` Mike Galbraith
2014-11-02  7:31   ` 3.14.23-rt20 - softirq: resurrect softirq threads Mike Galbraith
2015-02-17 13:05     ` Sebastian Andrzej Siewior
2015-02-17 14:00       ` Mike Galbraith

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=1415202259.5402.90.camel@marge.simpson.net \
    --to=umgwanakikbuti@gmail.com \
    --cc=C.Emde@osadl.org \
    --cc=bigeasy@linutronix.de \
    --cc=jkacur@redhat.com \
    --cc=juergh@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rt-users@vger.kernel.org \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    --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®