From: Russell King <rmk+lkml@arm.linux.org.uk>
To: George Anzinger <george@mvista.com>
Cc: Andi Kleen <ak@muc.de>, Dave Jones <davej@redhat.com>,
akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: tickle nmi watchdog whilst doing serial writes.
Date: Thu, 19 May 2005 08:33:39 +0100 [thread overview]
Message-ID: <20050519083338.A28946@flint.arm.linux.org.uk> (raw)
In-Reply-To: <428BDCAD.2090307@mvista.com>; from george@mvista.com on Wed, May 18, 2005 at 05:24:13PM -0700
On Wed, May 18, 2005 at 05:24:13PM -0700, George Anzinger wrote:
> Um... I would think the real fix is to set the UART up to generate the modem
> status interrupt and eliminate the pole loop. Why can't this be done? I, for
> one, don't want my cpu looping in the serial driver, even more so with the
> interrupt system off. This, in my mind, is a real bug in the serial driver and
> should be so handled.
Because printk is *synchronous*. It never returns until it's written
the entire message. There is no buffering.
Extra complexity, adding reliance on interrupts, etc all means that
you reduce the probability that you'll get the panic or oops message
out of the system.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-05-19 7:33 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-13 18:48 tickle nmi watchdog whilst doing serial writes Dave Jones
2005-05-13 19:14 ` Arjan van de Ven
2005-05-13 19:23 ` Dave Jones
2005-05-13 19:37 ` Russell King
2005-05-14 6:43 ` Andrew Morton
2005-05-14 6:57 ` Dave Jones
2005-05-14 7:07 ` Andrew Morton
2005-05-14 10:31 ` Ed Tomlinson
2005-05-14 10:53 ` Alexander Nyberg
2005-05-15 11:40 ` Andi Kleen
2005-05-14 10:53 ` Ed Tomlinson
2005-05-15 11:38 ` Andi Kleen
2005-05-15 12:07 ` Russell King
2005-05-15 12:20 ` Andi Kleen
2005-05-15 14:01 ` Russell King
2005-05-15 14:03 ` Andi Kleen
2005-05-19 0:24 ` George Anzinger
2005-05-19 7:33 ` Russell King [this message]
2005-05-23 20:20 ` Bill Davidsen
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=20050519083338.A28946@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=davej@redhat.com \
--cc=george@mvista.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox