From: Steven Rostedt <rostedt@goodmis.org>
To: Valdis.Kletnieks@vt.edu
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel <linux-kernel@vger.kernel.org>,
Serge Noiraud <serge.noiraud@bull.net>
Subject: Re: RT : nvidia driver and perhaps others
Date: Wed, 15 Jun 2005 10:45:54 -0400 [thread overview]
Message-ID: <1118846754.4508.20.camel@localhost.localdomain> (raw)
In-Reply-To: <200506151240.j5FCeO6l027298@turing-police.cc.vt.edu>
On Wed, 2005-06-15 at 08:40 -0400, Valdis.Kletnieks@vt.edu wrote:
> On Wed, 15 Jun 2005 10:21:45 +0200, Serge Noiraud said:
>
> > I try to compile the nvidia driver for my RT kernel.
> > It does not work anymore.
>
> You aren't going to get much sympathy here on that one...:)
You do from me :) I have a NVidia on two machines that I run RT on. But
they are both SMP (well one is just hyper threaded) and I couldn't get
them working with SMP. So I just use the vesa driver when running RT on
those machines :-( It's been several versions back since I had it
working on UP with NVidia (about a month or two back, which at Ingo's
speed is an eternity).
>
> > Isn't there a better way to avoid these modifications ?
> > for example to have the external fonction the same than non RT kernel.
> > and have an internal link to the new one or something like that ?
>
> However, he *does* have a point here - GPL'ed out-of-tree drivers will
> have these same issues. Yes, I know the standard "get them into the tree"
> refrain here...
Well, if local_irq_disable doesn't turn off irqs and you don't have it
bugging per Esben's patch, it shouldn't be a problem to just recompile
it again.
>
> > These drivers are proprietary, so I can't modify them.
>
> Fortunately, NVidia supplies enough pieces to make things work..
But you don't know what those pieces that you don't see do and if they
really need irqs disabled. I had to hack a little to get interrupts off
to call one of the NVidia's hooks. I don't really remember all that I
did, but I still wasn't able to get it working on SMP.
>
> > I think we should change :
> >
> > 1 - local_irq_* to raw_local_irq_* : is it always true ?
>
> > 2 - spin_* to raw_spin_* ?
>
> Ingo et al - what *is* the recommended magic to make a driver compile and
> work cleanly with or without RT? Hopefully there's a simple "will work correctly,
> but possibly sub-optimal latency" cookbook scheme....
Hopefully, just compiling the way it is would work. The idea of Ingo's
magic code is to have what is already in place work with RT.
-- Steve
prev parent reply other threads:[~2005-06-15 14:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-15 8:21 RT : nvidia driver and perhaps others Serge Noiraud
2005-06-15 12:40 ` Valdis.Kletnieks
2005-06-15 14:45 ` Steven Rostedt [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=1118846754.4508.20.camel@localhost.localdomain \
--to=rostedt@goodmis.org \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=serge.noiraud@bull.net \
/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