All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: 2.6.24 says "serial8250: too much work for irq4" a lot.
Date: Sat, 09 Feb 2008 13:36:05 -0800	[thread overview]
Message-ID: <47AE1CC5.10700@zytor.com> (raw)
In-Reply-To: <f43fc5580802090315u3561d9a5g428d8c9c05db74ce@mail.gmail.com>

Blue Swirl wrote:
>>
>> If you look at the patch, there are no timing dependencies; the only
>> parameter is the depth of the virtual queue.  The exhaustion is
>> completely controlled by target OS access patterns.
> 
> Thanks, this clarified the difference. But I'll rephrase my original comment:
> 
> The patch looks OK, but the simulated FIFO exhaustion should benefit
> all devices, as
> discussed here:
> http://lists.gnu.org/archive/html/qemu-devel/2007-12/msg00283.html

The difference is you *can't* do that in a general layer.

	-hpa

  reply	other threads:[~2008-02-09 21:36 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
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 [this message]
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=47AE1CC5.10700@zytor.com \
    --to=hpa@zytor.com \
    --cc=blauwirbel@gmail.com \
    --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 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.