public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
* serial problems cont..
@ 2008-08-31 20:57 Michael Malone
  2008-09-01  9:26 ` Avi Kivity
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Malone @ 2008-08-31 20:57 UTC (permalink / raw)
  To: kvm mailing list

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...)

Thanks,

Michael

=======================================================================
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.
=======================================================================


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: serial problems cont..
  2008-08-31 20:57 serial problems cont Michael Malone
@ 2008-09-01  9:26 ` Avi Kivity
  2008-09-02  1:25   ` Michael Malone
  0 siblings, 1 reply; 4+ messages in thread
From: Avi Kivity @ 2008-09-01  9:26 UTC (permalink / raw)
  To: Michael Malone; +Cc: kvm mailing list

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.

-- 
error compiling committee.c: too many arguments to function


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: serial problems cont..
  2008-09-01  9:26 ` Avi Kivity
@ 2008-09-02  1:25   ` Michael Malone
  2008-09-02  8:32     ` Avi Kivity
  0 siblings, 1 reply; 4+ messages in thread
From: Michael Malone @ 2008-09-02  1:25 UTC (permalink / raw)
  To: kvm mailing list; +Cc: Avi Kivity

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.
=======================================================================


^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: serial problems cont..
  2008-09-02  1:25   ` Michael Malone
@ 2008-09-02  8:32     ` Avi Kivity
  0 siblings, 0 replies; 4+ messages in thread
From: Avi Kivity @ 2008-09-02  8:32 UTC (permalink / raw)
  To: Michael Malone; +Cc: kvm mailing list

Michael Malone wrote:
>>
>> 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.

I meant 
http://git.kernel.org/?p=linux/kernel/git/avi/kvm-userspace.git;a=commit;h=02f0b4c0cc26f3a2578d515d96781f5a6258888d 
.  But since it doesn't seem to solve your problems (it is part of 
kvm-74), more work is needed.

-- 
error compiling committee.c: too many arguments to function


^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2008-09-02  8:32 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2008-08-31 20:57 serial problems cont Michael Malone
2008-09-01  9:26 ` Avi Kivity
2008-09-02  1:25   ` Michael Malone
2008-09-02  8:32     ` Avi Kivity

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox