From: Abramo Bagnara <abramo@alsa-project.org>
To: Andrew Morton <andrewm@uow.edu.au>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, Pavel Machek <pavel@suse.cz>,
Tom Eastep <teastep@seattlefirewall.dyndns.org>,
"Michael B. Trausch" <fd0man@crosswinds.net>,
Josh Myer <jbm@joshisanerd.com>,
linux-kernel@vger.kernel.org
Subject: Re: [OT] Major Clock Drift
Date: Tue, 13 Feb 2001 08:24:16 +0100 [thread overview]
Message-ID: <3A88E120.284CCBC2@alsa-project.org> (raw)
In-Reply-To: <20010212113213.B235@bug.ucw.cz> from "Pavel Machek" at Feb 12, 2001 11:32:13 AM <E14SGLm-0006es-00@the-village.bc.nu> <3A87CB3B.B05C03B5@uow.edu.au>
Andrew Morton wrote:
>
> Alan Cox wrote:
> >
> > > > queued_writes=1;
> > > > return;
> > > > }
> > > > }
> > >
> > > Unfortunately, that means that if machine crashes in interrupt, it may
> > > "loose" printk message. That is considered bad (tm).
> >
> > The alternative is that the machine clock slides continually and the machine
> > is unusable. This is considered even worse by most people
>
> Neither. I was going to dust off my enhanced "bust_spinlocks"
> patch which sets a little flag when we're doing an
> oops, BUG(), panic() or die(). If the flag
> is set, printk() just punches through the lock.
IMO to treat this as an exception it's not the right solution.
A better alternative is to flush one entry of Alan proposed queue on the
following conditions:
- in_interrupt() is true AND queue is full
--
Abramo Bagnara mailto:abramo@alsa-project.org
Opera Unica Phone: +39.546.656023
Via Emilia Interna, 140
48014 Castel Bolognese (RA) - Italy
ALSA project is http://www.alsa-project.org
sponsored by SuSE Linux http://www.suse.com
It sounds good!
next prev parent reply other threads:[~2001-02-13 7:28 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
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 [this message]
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=3A88E120.284CCBC2@alsa-project.org \
--to=abramo@alsa-project.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=andrewm@uow.edu.au \
--cc=fd0man@crosswinds.net \
--cc=jbm@joshisanerd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
--cc=teastep@seattlefirewall.dyndns.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.