From: Rob Landley <rob@landley.net>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Ingo Molnar <mingo@elte.hu>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.24 says "serial8250: too much work for irq4" a lot.
Date: Thu, 7 Feb 2008 14:13:44 -0600 [thread overview]
Message-ID: <200802071413.45085.rob@landley.net> (raw)
In-Reply-To: <47AB41C8.3010001@zytor.com>
On Thursday 07 February 2008 11:37:12 H. Peter Anvin wrote:
> > actually, the way i solved it for qemu+KVM+paravirt was to just turn off
> > this rather silly check in the serial driver if inside a paravirt guest.
> > When we are emulated then the serial 'hardware' is totally reliable and
> > we should just trust it. That way i never dropped a single bit of kernel
> > log output again.
>
> Yes, but keying that on paravirt is silly in the extreme. After all,
> there is no need for this to be paravirtualized.
>
> -hpa
Specifically, qemu isn't paravirtualized, it's fully virtualized. The same
kernel can run on real hardware just fine. (Sort of the point of the
project...)
I can yank the warning for the kernels I build (or set PASS_LIMIT to 9999999),
but I'd rather not carry any more patches than I can avoid...
Rob
--
"One of my most productive days was throwing away 1000 lines of code."
- Ken Thompson.
next prev parent reply other threads:[~2008-02-07 20:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 20:55 2.6.24 says "serial8250: too much work for irq4" a lot Rob Landley
2008-02-05 21:07 ` H. Peter Anvin
2008-02-06 0:43 ` [Qemu-devel] " Rob Landley
2008-02-07 12:39 ` Ingo Molnar
2008-02-07 17:37 ` H. Peter Anvin
2008-02-07 20:13 ` Rob Landley [this message]
2008-02-07 20:53 ` H. Peter Anvin
2008-02-07 21:19 ` H. Peter Anvin
2008-02-08 7:04 ` Rob Landley
2008-02-09 5:49 ` [Qemu-devel] " Rob Landley
2008-02-09 7:04 ` Blue Swirl
2008-02-09 7:12 ` H. Peter Anvin
2008-02-09 11:15 ` Blue Swirl
2008-02-09 21:36 ` H. Peter Anvin
2008-02-10 8:01 ` Blue Swirl
2008-02-10 11:26 ` Paul Brook
2008-03-11 23:51 ` Aurelien Jarno
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=200802071413.45085.rob@landley.net \
--to=rob@landley.net \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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.