All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] high resolution timer question
Date: Mon, 10 Dec 2007 12:01:34 -0600	[thread overview]
Message-ID: <475D7EFE.7060309@codemonkey.ws> (raw)
In-Reply-To: <f43fc5580712100951y152d48d9pe0df6eaed0d098a0@mail.gmail.com>

Blue Swirl wrote:
> On 12/10/07, Robert Reif <reif@earthlink.net> wrote:
>   
>> Writing data to a serial port on the sparc emulation happens immediately.
>> I would like to throttle the write speed to match the actual baud rate.
>> What's the best way to do this in qemu?  Will QEMUTimer work for a
>> 1 millisecond timer?
>>     
>
> Do you mean that you want the serial port to match the host speed so
> that for example, at 9600 baud, target would only receive 9600 bits
> per second? Or do you mean that the emulated CPU should see bits
> arriving at the same rate that the real CPU would see compared to CPU
> execution speed?
>
> On the positive side, this would fix a bug with serial interrupts
> arriving too fast which can trigger Linux panics. But this would also
> complicate the design because currently the devices do not need to
> emulate any internal buffers.
>
> I think the throttling should be done at CharDriver level so that all
> targets and also other devices, like parallel ports (SUNW,bpp anyone?)
>   

But the timing is entirely a concept of the hardware devices.  It seems 
like it would be easier to just add a growable buffer, and then setup a 
timer in each device that reads from the buffer.

Regards,

Anthony Liguori

> can benefit. It should be turned off when talking to real hardware on
> the host.
>
>
>
>   

  reply	other threads:[~2007-12-10 18:01 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 12:59 [Qemu-devel] high resolution timer question Robert Reif
2007-12-10 15:16 ` Arnon Gilboa
2007-12-10 17:51 ` Blue Swirl
2007-12-10 18:01   ` Anthony Liguori [this message]
2007-12-11  1:17     ` Paul Brook
2007-12-12  1:02   ` Robert Reif
2007-12-12  2:21     ` Robert Reif
2007-12-12  3:23       ` Robert Reif

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=475D7EFE.7060309@codemonkey.ws \
    --to=anthony@codemonkey.ws \
    --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.