summaryrefslogtreecommitdiffstats
path: root/drivers/tty
diff options
context:
space:
mode:
authorJiri Slaby <jirislaby@gmail.com>2011-06-05 22:51:49 +0200
committerGreg Kroah-Hartman <gregkh@suse.de>2011-06-07 09:44:36 -0700
commite7328ae1848966181a7ac47e8ae6cddbd2cf55f3 (patch)
tree8261430b83cce0fea0ae0a8ca8c626d66bd4be7e /drivers/tty
parent2807190b69f60ce4a04a9c7c523c9bce8cb62b2e (diff)
downloadlinux-e7328ae1848966181a7ac47e8ae6cddbd2cf55f3.tar.gz
linux-e7328ae1848966181a7ac47e8ae6cddbd2cf55f3.tar.bz2
linux-e7328ae1848966181a7ac47e8ae6cddbd2cf55f3.zip
serial: 8250, increase PASS_LIMIT
With virtual machines like qemu, it's pretty common to see "too much work for irq4" messages nowadays. This happens when a bunch of output is printed on the emulated serial console. This is caused by too low PASS_LIMIT. When ISR loops more than the limit, it spits the message. I've been using a kernel with doubled the limit and I couldn't see no problems. Maybe it's time to get rid of the message now? Signed-off-by: Jiri Slaby <jirislaby@gmail.com> Cc: Alan Cox <alan@linux.intel.com> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
Diffstat (limited to 'drivers/tty')
-rw-r--r--drivers/tty/serial/8250.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/drivers/tty/serial/8250.c b/drivers/tty/serial/8250.c
index b40f7b90c81d..f11df87fa249 100644
--- a/drivers/tty/serial/8250.c
+++ b/drivers/tty/serial/8250.c
@@ -81,7 +81,7 @@ static unsigned int skip_txen_test; /* force skip of txen test at init time */
#define DEBUG_INTR(fmt...) do { } while (0)
#endif
-#define PASS_LIMIT 256
+#define PASS_LIMIT 512
#define BOTH_EMPTY (UART_LSR_TEMT | UART_LSR_THRE)