From: "Jaswinder Singh" <jaswinderlinux@gmail.com>
To: "Ingo Molnar" <mingo@elte.hu>
Cc: "Nick Piggin" <nickpiggin@yahoo.com.au>,
"Mike Galbraith" <efault@gmx.de>,
"Steven Rostedt" <rostedt@goodmis.org>,
LKML <linux-kernel@vger.kernel.org>,
RT <linux-rt-users@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>
Subject: Re: [2.6.23-rt3] NMI watchdog trace of deadlock
Date: Sat, 27 Oct 2007 15:42:32 +0530 [thread overview]
Message-ID: <3f9a31f40710270312o5a4eb79exa67ed63b4f084f9e@mail.gmail.com> (raw)
In-Reply-To: <20071027094407.GA12047@elte.hu>
Hello Ingo,
On 10/27/07, Ingo Molnar <mingo@elte.hu> wrote:
>
> it's not atomic interrupt context but irq thread context - and -rt
> remaps kmap_atomic() to kmap() internally.
>
> the problem seems to be what Mike's patch works around: fiddling with
> irq flags in the ntfs code. That fiddling seems quite unnecessary at
> first sight.
>
Is this a nice idea to go inside device drivers and filesystem and
make changes in kernel source code to enable RT.
RT related change should be in header files, so that we don't need to
make changes for drivers or filesystem source files.
And when user will disable RT then these patches will again make problems.
We need to find some better alternative.
Thank you,
Jaswinder Singh.
next prev parent reply other threads:[~2007-10-27 10:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-24 17:07 2.6.23-rt2 Steven Rostedt
2007-10-27 5:21 ` [2.6.23-rt3] NMI watchdog trace of deadlock Mike Galbraith
2007-10-27 9:15 ` Nick Piggin
2007-10-27 9:43 ` Mike Galbraith
2007-10-27 9:44 ` Ingo Molnar
2007-10-27 10:12 ` Jaswinder Singh [this message]
2007-10-27 13:22 ` Steven Rostedt
2007-10-27 10:17 ` Mike Galbraith
2007-10-27 13:16 ` Ingo Molnar
2007-10-27 14:29 ` Steven Rostedt
2007-10-27 9:40 ` 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=3f9a31f40710270312o5a4eb79exa67ed63b4f084f9e@mail.gmail.com \
--to=jaswinderlinux@gmail.com \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nickpiggin@yahoo.com.au \
--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 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®