From: Christoph Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Daniel Vacek <neelx.g@gmail.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Date: Tue, 15 Nov 2016 14:29:16 -0600 (CST) [thread overview]
raw)
> > There is a deadlock, Peter!!!
>
> Describe please? Also, have you tried disabling RT_RUNTIME_SHARE ?
>
The description was given earlier in the the thread and the drawbacks of
using RT_RUNTIME_SHARE as well.
WARNING: multiple messages have this Message-ID (diff)
From: Christoph Lameter <cl@linux.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Daniel Vacek <neelx.g@gmail.com>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Tommaso Cucinotta <tommaso.cucinotta@sssup.it>,
LKML <linux-kernel@vger.kernel.org>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Ingo Molnar <mingo@redhat.com>
Subject: (unknown)
Date: Tue, 15 Nov 2016 14:29:16 -0600 (CST) [thread overview]
Message-ID: <alpine.DEB.2.20.1611151428190.28591@east.gentwo.org> (raw)
> > There is a deadlock, Peter!!!
>
> Describe please? Also, have you tried disabling RT_RUNTIME_SHARE ?
>
The description was given earlier in the the thread and the drawbacks of
using RT_RUNTIME_SHARE as well.
next reply other threads:[~2016-11-15 20:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-15 20:29 Christoph Lameter [this message]
2016-11-15 20:29 ` (unknown) Christoph Lameter
2016-11-15 21:58 ` ??? Steven Rostedt
2016-11-16 10:40 ` your mail Peter Zijlstra
2016-11-16 14:25 ` Steven Rostedt
2016-11-16 14:28 ` Peter Zijlstra
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=alpine.DEB.2.20.1611151428190.28591@east.gentwo.org \
--to=cl@linux.com \
--cc=bristot@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=neelx.g@gmail.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tommaso.cucinotta@sssup.it \
/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.