From: Mike Galbraith <mgalbraith@suse.de>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
rt-users <linux-rt-users@vger.kernel.org>
Subject: SUSE question wrt RT locking primitives
Date: Fri, 13 Apr 2012 07:34:16 +0200 [thread overview]
Message-ID: <1334295256.9525.60.camel@marge.simpson.net> (raw)
In-Reply-To: <1321303871.5011.6.camel@frodo>
Greetings,
SUSE is looking for a straight up answer, I've been tasked with asking
the question: can RT maintainers be convinced to fix the RT tree such
that locking primitives do not switch from 'OK' to TABOO' at the flick
of a config switch? It is understood that "yes" may have undesirable
side-effects :)
Background:
The migrate_enable/disable() EXPORT_SYMBOL_GPL thing came up yesterday
again with yet another customer stuck using yet another proprietary
driver for proprietary hardware. The choice for the customer/user is
use what exists, knock on proprietary doors, or go look at platforms
where the proprietary gizmo they need or want to use just works.
So that's where the question comes from. Life would be easier if RT
didn't trigger the Dr. Jeckle -> Mr. Hyde thing. You know all about
where what happens to which locks, so I'll just snip what I had quoted
and needlessly commented on to keep this as short as possible ;-)
-Mike
next prev parent reply other threads:[~2012-04-13 5:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-14 1:44 [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break John Kacur
2011-11-14 1:44 ` John Kacur
2011-11-14 1:44 ` [PATCH 2/2] Compile error with allmodconfig and CONFIG_PREEMPT_RT_FULL=y John Kacur
2011-11-14 16:51 ` Paul E. McKenney
2011-11-14 17:39 ` John Kacur
2011-11-14 17:57 ` Paul E. McKenney
2011-11-14 20:51 ` Steven Rostedt
2011-11-14 21:07 ` John Kacur
2011-11-14 21:07 ` John Kacur
2011-11-15 5:22 ` Mike Galbraith
2011-11-15 12:23 ` Steven Rostedt
2011-11-15 13:27 ` Mike Galbraith
2011-11-15 13:45 ` Mike Galbraith
2011-11-16 14:21 ` Mike Galbraith
2012-04-13 5:34 ` Mike Galbraith [this message]
2012-04-13 12:58 ` SUSE question wrt RT locking primitives Steven Rostedt
2012-04-13 14:53 ` Mike Galbraith
2012-04-13 15:47 ` Thomas Gleixner
2011-11-14 16:50 ` [PATCH 1/2] v3.2-rc1-52e4c2a05-rt1 fix for compile break Paul E. McKenney
2011-11-14 20:57 ` Steven Rostedt
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=1334295256.9525.60.camel@marge.simpson.net \
--to=mgalbraith@suse.de \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.