From: Andi Kleen <freitag@alancoxonachip.com>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org
Subject: Re: [OT] Major Clock Drift
Date: 12 Feb 2001 11:05:18 +0100 [thread overview]
Message-ID: <ouplmrckyht.fsf@pigdrop.muc.suse.de> (raw)
In-Reply-To: <E14SFbG-0006WR-00@the-village.bc.nu>
In-Reply-To: Alan Cox's message of "12 Feb 2001 10:54:49 +0100"
Alan Cox <alan@lxorguk.ukuu.org.uk> writes:
> Suppose vesafb did something like this, dropping the printk lock
>
> if(test_and_set_bit(0, &vesafb_lock))
> {
> if(in_interrupt())
> {
> // remember which bit of the dmesg ring to queue
> queued_writes=1;
> return;
Just what happens when you run out of dmesg ring in an interrupt ?
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-02-12 10:06 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-04 4:32 [OT] Major Clock Drift Josh Myer
2001-02-04 4:42 ` Manfred Bartz
2001-02-04 12:56 ` Michael B. Trausch
2001-02-04 15:18 ` Steve Underwood
2001-02-04 15:31 ` Hacksaw
2001-02-04 23:46 ` Alan Chandler
2001-02-04 17:18 ` Tom Eastep
2001-02-04 18:04 ` Hacksaw
2001-02-04 18:07 ` Tom Eastep
2001-02-05 13:25 ` Andrew Morton
2001-02-10 21:58 ` Pavel Machek
2001-02-11 11:05 ` Andrew Morton
2001-02-11 11:06 ` Pavel Machek
2001-02-11 11:47 ` Andrew Morton
2001-02-11 12:14 ` Peter Horton
2001-02-11 13:52 ` Chris Wedgwood
2001-02-05 1:18 ` Michael B. Trausch
2001-02-13 3:00 ` george anzinger
2001-02-13 6:51 ` Josh Myer
2001-02-10 21:58 ` [OT] " Pavel Machek
2001-02-11 17:07 ` Alan Cox
2001-02-11 22:29 ` Andrew Morton
2001-02-12 9:48 ` Alan Cox
2001-02-12 10:05 ` Andi Kleen [this message]
2001-02-12 10:10 ` Alan Cox
2001-02-12 12:14 ` James Sutherland
2001-02-12 10:32 ` Pavel Machek
2001-02-12 10:36 ` Alan Cox
2001-02-12 11:38 ` Andrew Morton
2001-02-13 7:24 ` Abramo Bagnara
2001-02-10 21:55 ` Pavel Machek
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=ouplmrckyht.fsf@pigdrop.muc.suse.de \
--to=freitag@alancoxonachip.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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.