From: Ingo Molnar <mingo@elte.hu>
To: Amit Shah <amit.shah@codito.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RT-V0.7.22 Bug with fbdev and e100
Date: Tue, 9 Nov 2004 13:22:42 +0100 [thread overview]
Message-ID: <20041109122242.GA25077@elte.hu> (raw)
In-Reply-To: <20041109121330.GA23533@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
> [...] This will reduce the utility of fbcon when debugging kernel
> crashes, but it should avoid this assert [...]
in fact the way i implemented it in my tree:
#define in_atomic_rt() (!oops_in_progress && (in_atomic() || irqs_disabled()))
still enables crash messages to make it to fbcon. So the only thing
skipped will be non-fatal messages printed from 'raw' critical sections.
(which are very rare in PREEMPT_RT kernels).
Ingo
prev parent reply other threads:[~2004-11-09 11:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 10:53 RT-V0.7.22 Bug with fbdev and e100 Amit Shah
2004-11-09 12:13 ` Ingo Molnar
2004-11-09 12:22 ` Ingo Molnar [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=20041109122242.GA25077@elte.hu \
--to=mingo@elte.hu \
--cc=amit.shah@codito.com \
--cc=linux-kernel@vger.kernel.org \
/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.