From: Thomas Gleixner <tglx@linutronix.de>
To: Andi Kleen <ak@suse.de>
Cc: Daniel Walker <dwalker@mvista.com>,
Sven-Thorsten Dietrich <thebigcorporation@gmail.com>,
mingo@elte.hu, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] Don't sleep in oops_begin()
Date: Tue, 18 Sep 2007 10:30:51 +0200 [thread overview]
Message-ID: <1190104251.2995.66.camel@chaos> (raw)
In-Reply-To: <200709181005.49542.ak@suse.de>
On Tue, 2007-09-18 at 10:05 +0200, Andi Kleen wrote:
> > > I disagree for the oops case. You want the simplest possible code
> > > here.
> >
> > If that's true for real time , should be true for mainline right?
>
> You mean it shouldn't use lockdep etc. there? Yes good point. I can change
> that
Yes, the oops code path should be as decoupled as possible. We want to
know what happened in the first place and not what consequential damage
is caused by the initial problem.
tglx
next prev parent reply other threads:[~2007-09-18 8:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-17 18:12 [PATCH] Don't sleep in oops_begin() Andi Kleen
2007-09-17 18:28 ` Daniel Walker
2007-09-17 18:46 ` Andi Kleen
2007-09-17 18:54 ` Daniel Walker
2007-09-17 19:00 ` Andi Kleen
2007-09-17 19:07 ` Daniel Walker
2007-09-17 19:38 ` Sven-Thorsten Dietrich
2007-09-17 20:20 ` Andi Kleen
2007-09-17 20:30 ` Sven-Thorsten Dietrich
2007-09-18 0:10 ` Daniel Walker
2007-09-18 8:05 ` Andi Kleen
2007-09-18 8:30 ` Thomas Gleixner [this message]
2007-09-17 23:13 ` Gregory Haskins
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=1190104251.2995.66.camel@chaos \
--to=tglx@linutronix.de \
--cc=ak@suse.de \
--cc=dwalker@mvista.com \
--cc=linux-rt-users@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=thebigcorporation@gmail.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 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.