LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Pavel Machek <pavel@ucw.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Benjamin LaHaise <bcrl@kvack.org>,
akpm@osdl.org, linux-serial@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: remove "too much work for irq" printk
Date: Sun, 13 Jan 2008 23:03:27 +0100 [thread overview]
Message-ID: <20080113220327.GB5128@elf.ucw.cz> (raw)
In-Reply-To: <20080112212457.3bf534af@lxorguk.ukuu.org.uk>
On Sat 2008-01-12 21:24:57, Alan Cox wrote:
> On Sat, 12 Jan 2008 15:15:43 -0500
> Benjamin LaHaise <bcrl@kvack.org> wrote:
>
> > When using kvm with a serial console, the serial driver will print out
> > "too much work for irq4" on any heavy activity (ie vi on a file repainting
> > the terminal). This message is entirely spurious, as output continues to
> > work fine. Remove the message as it corrupts screen output and is far too
> > easy to trigger.
>
> NAK. This is a qemu/kvm emulation bug. The real check is there to catched
> jammed IRQs and combined with the IRQ bug handling nowdays does actually
> do the intended job.
>
> Our serial port code (correctly) interprets a continuous stream of bytes
> at an impossible bit rate as an error. KVM should be emulating to some
> extent at least the timing on serial interfaces or using a virtualised
> interface.
How can you tell apart impossible bit rate from really slow CPU, or
maybe just an SMI storm, or heavy busmaster DMA?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2008-01-13 22:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-12 20:15 [PATCH] serial: remove "too much work for irq" printk Benjamin LaHaise
2008-01-12 20:21 ` Christoph Hellwig
2008-01-12 21:24 ` Alan Cox
2008-01-12 21:39 ` H. Peter Anvin
2008-01-12 21:42 ` Alan Cox
2008-01-12 21:58 ` H. Peter Anvin
2008-01-13 22:03 ` Pavel Machek [this message]
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=20080113220327.GB5128@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bcrl@kvack.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@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;
as well as URLs for NNTP newsgroup(s).