From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@muc.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: overlaping printk
Date: Thu, 20 May 2004 17:19:39 +0200 [thread overview]
Message-ID: <20040520151939.GA3562@elte.hu> (raw)
In-Reply-To: <m3lljnnoa0.fsf@averell.firstfloor.org>
* Andi Kleen <ak@muc.de> wrote:
> One alternative way would be to use locks with timeouts for these two
> locks (e.g. checking the TSC on x86, since the timer interrupt may not
> be running anymore) and only break the lock when the wait time is too
> long.
>
> Of course serial lines can be quite slow so even that may not help
> always (for unknown reasons far too many people use 9600 baud for
> their serial line)
another solution would be to break the lock only once during the
kernel's lifetime. The system is messed up anyway if it needs multiple
lock breaks to get an oops out to the console. We dont care about
followup oopses - the first oops is that matters.
Ingo
next prev parent reply other threads:[~2004-05-20 15:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1XBEP-Mc-49@gated-at.bofh.it>
[not found] ` <1XBXw-13D-3@gated-at.bofh.it>
[not found] ` <1XWpp-zy-9@gated-at.bofh.it>
2004-05-20 14:53 ` overlaping printk Andi Kleen
2004-05-20 15:19 ` Ingo Molnar [this message]
2004-05-20 15:53 ` Ingo Molnar
2004-05-20 16:19 ` Andy Isaacson
2004-05-20 18:57 ` Ingo Molnar
2004-05-20 23:11 ` Andrew Morton
2004-05-21 7:00 ` Ingo Molnar
2004-05-19 15:55 Tuukka Toivonen
2004-05-19 16:03 ` Ricky Beam
2004-05-20 14:03 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2004-05-19 15:19 Ricky Beam
2004-05-19 15:26 ` Tigran Aivazian
2004-05-19 15:31 ` Ricky Beam
2004-05-19 15:39 ` Randy.Dunlap
2004-05-20 7:21 ` Andrew Morton
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=20040520151939.GA3562@elte.hu \
--to=mingo@elte.hu \
--cc=ak@muc.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox