qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: Blue Swirl <blauwirbel@gmail.com>
Subject: Re: [Qemu-devel] Timers
Date: Wed, 23 May 2007 18:18:58 +0100	[thread overview]
Message-ID: <200705231818.59906.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580705231000h36e03e1exb277bd9c219fbdf8@mail.gmail.com>

On Wednesday 23 May 2007, Blue Swirl wrote:
> On 5/23/07, Paul Brook <paul@codesourcery.com> wrote:
> > I get fed up of having to re-implement a simple countdown timer for every
> > new board, so I've added a simple periodic timer implementation to cvs
> > (ptimer.c). Currently only the Arm PrimeCell based boards use this, but
> > I've a few other uses in the pipeline.
>
> Nice idea! On Sparc the timer can be configured to work in 64-bit
> mode, so could the ptimer_get/set_count be changed to use 64-bit
> values?

In principle yes, though you may have to be careful to avoid overflows.

The current API supports specifying either frequency (better for fast, large 
count timers) and period (better for slow, small count timers). We want to 
avoid breaking either extreme when adding 64-bit counters.

Paul

  reply	other threads:[~2007-05-23 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-23  0:06 [Qemu-devel] Timers Paul Brook
2007-05-23  0:52 ` George G. Davis
2007-05-23  1:14   ` Paul Brook
2007-05-23  1:39     ` George G. Davis
2007-05-23 17:00 ` Blue Swirl
2007-05-23 17:18   ` Paul Brook [this message]
2007-05-23 19:28     ` Blue Swirl
2007-05-23 19:48       ` Paul Brook
2007-05-23 20:53         ` andrzej zaborowski
2007-05-23 21:56           ` Paul Brook
2007-05-24 19:18             ` Blue Swirl
2007-05-24 19:28               ` Paul Brook
2007-05-23 17:25   ` George G. Davis
2007-05-23 17:58     ` Paul Brook

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=200705231818.59906.paul@codesourcery.com \
    --to=paul@codesourcery.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).