All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matt Mackall <mpm@selenic.com>
To: Benny Amorsen <benny+usenet@amorsen.dk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: IRQ off latency of printk is very high
Date: Fri, 26 Oct 2007 15:28:31 -0500	[thread overview]
Message-ID: <20071026202831.GP17536@waste.org> (raw)
In-Reply-To: <m3r6jighjl.fsf@ursa.amorsen.dk>

On Fri, Oct 26, 2007 at 02:57:18PM +0200, Benny Amorsen wrote:
> >>>>> "MM" == Matt Mackall <mpm@selenic.com> writes:
> 
> MM> Well there are things we can do, yes, but I'd be worried that
> MM> they've give up the deterministic behavior we rely on quite
> MM> heavily for debugging. If event A happens before event B, we must
> MM> see the message from A before the one from B, even if B happens in
> MM> irq context.
> 
> MM> And if event B is a hard lock up, we'd also like to be sure the
> MM> message for A actually gets out. If B happens in the interrupt
> MM> that comes in when we re-enable them, that won't happen.
> 
> I can see the concerns, but right now it all leads to disabling serial
> console for real-time servers. That is even less helpful for
> debugging.

That's not clear. No data is often better than false or misleading
data.

-- 
Mathematics is the supreme nostalgia of our time.

  reply	other threads:[~2007-10-26 20:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-25 19:44 IRQ off latency of printk is very high Tim Bird
2007-10-25 20:19 ` Matt Mackall
2007-10-25 21:15   ` Tim Bird
2007-10-25 22:28 ` Mathieu Desnoyers
2007-10-25 22:52   ` Tim Bird
2007-10-25 23:12     ` Matt Mackall
2007-10-25 23:41       ` Tim Bird
2007-10-26  1:23         ` Matt Mackall
2007-10-26 12:57           ` Benny Amorsen
2007-10-26 20:28             ` Matt Mackall [this message]
2007-10-29 18:54         ` Pavel Machek
2007-11-01 15:27           ` Mathieu Desnoyers
2007-11-01 21:11             ` Pavel Machek
2007-11-01 22:19               ` Mathieu Desnoyers

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=20071026202831.GP17536@waste.org \
    --to=mpm@selenic.com \
    --cc=benny+usenet@amorsen.dk \
    --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.