From: Stefan Weil <weil@mail.berlios.de>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] serial8250: too much work for irq4
Date: Sun, 15 Apr 2007 16:39:50 +0200 [thread overview]
Message-ID: <46223936.4000907@mail.berlios.de> (raw)
In-Reply-To: <46223117.9050301@bandsman.co.uk>
QEMU only emulates a serial interface without FIFO,
so Linux gets one interrupt per character sent or received.
And the emulation does not emulate the original speed
of the serial interface, but runs at fastest speed possible.
I get this log message every time when a program writes
more than a few lines, for example with QEMU emulating
Linux/MIPS when I start aptitude or call dmesg.
Without a working FIFO emulation, there is not much you
can do if you really need a serial console or other kind of
serial communication.
Stefan
Nigel Horne schrieb:
> In the mips emulator I often see "serial8250: too much work for irq4",
> particularity when running vi etc. Is that to be expected, and known
> about?
> If so, please ignore this ;-), if not, I thought you may like to know.
>
> -Nigel
prev parent reply other threads:[~2007-04-15 14:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 14:05 [Qemu-devel] serial8250: too much work for irq4 Nigel Horne
2007-04-15 14:39 ` Stefan Weil [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=46223936.4000907@mail.berlios.de \
--to=weil@mail.berlios.de \
--cc=qemu-devel@nongnu.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).