qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: qemu-devel@nongnu.org
Cc: "George G. Davis" <davis_g@comcast.net>
Subject: Re: [Qemu-devel] Timers
Date: Wed, 23 May 2007 18:58:28 +0100	[thread overview]
Message-ID: <200705231858.29299.paul@codesourcery.com> (raw)
In-Reply-To: <20070523172550.GE3110@mvista.com>

> > 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?
>
> Perhaps the width could be made runtime configurable, e.g. 16, 24, 32,
> 64-bits as required for a given system, since there are other targets
> which may need differring widths (mind I haven't looked all too closely
> at the code to see if it already handles this : ).  Likewise, perhaps
> up/down count can also be made runtime configurable, since, again, some
> targets implement up counters.  The logic is all the same in that
> case, with just a difference in sign...

I don't think there's any point. A 64-bit countdown timer is sufficient to 
implement everything, and I'd expect the overhead is going to minimal. 
Converting a count-down timer into a count-up timer is trivial. The ARM 
timers are actually count-up timers.

Paul

      reply	other threads:[~2007-05-23 17:58 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
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 [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=200705231858.29299.paul@codesourcery.com \
    --to=paul@codesourcery.com \
    --cc=davis_g@comcast.net \
    --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).