From: Jan Kiszka <jan.kiszka@web.de>
To: Paul Brook <paul@codesourcery.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] 8250: more realistic TX-done IRQ rate
Date: Sun, 13 Apr 2008 10:05:30 +0200 [thread overview]
Message-ID: <4801BECA.1040303@web.de> (raw)
In-Reply-To: <4800ED38.1080003@web.de>
[-- Attachment #1: Type: text/plain, Size: 1053 bytes --]
Jan Kiszka wrote:
> Paul Brook wrote:
>> On Saturday 12 April 2008, Jan Kiszka wrote:
>> I'd also expect you to have the same problem with the RX queue. If you
>> don't it's a bug elsewhere in qemu.
>>
>>> + qemu_mod_timer(s->tx_timer, 1000 / (11520 / s->divider));
>>
>> This looks bogus. I think you're a few orders of magnitude out in your
>> timing calculations. As mentioned above, in practice you unlikely to
>> get anywhere
>> near the necessary realtime performance out of qemu.
>
> That depends. Current Linux distros typically have
> CONFIG_HIGH_RES_TIMERS enabled. But, of course, not many OSes QEMU works
> on have such support at all, and even Linux may decided to work without
> it for various reasons.
OK, that line was totally bogus. Somehow I once assumed that
qemu_mod_timer takes relative timeout (though I've used it with absolute
dates before). A new version will follow soon, which in fact triggered a
second patch for another issue of the current emulation - the hard-coded
baudbase.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]
prev parent reply other threads:[~2008-04-13 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-12 14:56 [Qemu-devel] [PATCH] 8250: more realistic TX-done IRQ rate Jan Kiszka
2008-04-12 16:47 ` [Qemu-devel] " Jan Kiszka
2008-04-12 16:48 ` [Qemu-devel] " Paul Brook
2008-04-12 17:11 ` Jan Kiszka
2008-04-13 8:05 ` Jan Kiszka [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=4801BECA.1040303@web.de \
--to=jan.kiszka@web.de \
--cc=paul@codesourcery.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.