From: Michael Malone <michael.malone@tait.co.nz>
To: kvm mailing list <kvm@vger.kernel.org>
Cc: Avi Kivity <avi@qumranet.com>
Subject: Re: serial problems cont..
Date: Tue, 02 Sep 2008 13:25:57 +1200 [thread overview]
Message-ID: <48BC9625.1010103@tait.co.nz> (raw)
In-Reply-To: <48BBB558.6060909@qumranet.com>
Avi Kivity wrote:
> Michael Malone wrote:
>> Hi everyone,
>>
>> I've written a couple of questions regarding the serial device in
>> KVM. After slightly more investigation I think I have found what's
>> going awry. Correct me if I'm wrong, but I believe that KVM
>> generates an interrupt for every single character it sends through
>> the serial port. This throws CPU usage through the roof and I
>> suspect this means that the timers aren't being handled correctly and
>> it failed on a string of 0's for me due to the timing slips.
>> GNU/Linux and Windows don't have anywhere near the processor usage
>> for their serial ports. Now, I know nothing of serial programming
>> and don't have any time to investigate it too heavily just now, but I
>> have pulled down the source and had a look through that, but it looks
>> to be doing the right thing (I suppose?). I was mainly wondering
>> how GNU/Linux and windows handle serial interrupts or if some of the
>> serial character events could be buffered, rather than overload the
>> processor? I guess this is a low priority for you, but any help
>> would be greatly appreciated (And when I have some more time, I will
>> spend some of it helping to develop KVM! Quid pro quo, Clarice...)
>>
>
> What version of kvm are you testing? There were some changes to the
> serial emulation recently. See for example
> 02f0b4c0cc26f3a2578d515d96781f5a6258888d in kvm-73.
>
I have tried with kvm 62, 69, 72 and 74. All of them gave the same
result. What do you mean by "See for example
02f0b4c0cc26f3a2578d515d96781f5a6258888d"?
- I am running Ubuntu 8.04 (Hardy) as host and Windows XP as guest on an
Intel Core 2 duo processor.
=======================================================================
This email, including any attachments, is only for the intended
addressee. It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
altered or corrupted during transmission.
=======================================================================
next prev parent reply other threads:[~2008-09-02 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-31 20:57 serial problems cont Michael Malone
2008-09-01 9:26 ` Avi Kivity
2008-09-02 1:25 ` Michael Malone [this message]
2008-09-02 8:32 ` Avi Kivity
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=48BC9625.1010103@tait.co.nz \
--to=michael.malone@tait.co.nz \
--cc=avi@qumranet.com \
--cc=kvm@vger.kernel.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