All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Brook <paul@codesourcery.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Timers
Date: Wed, 23 May 2007 20:48:15 +0100	[thread overview]
Message-ID: <200705232048.16793.paul@codesourcery.com> (raw)
In-Reply-To: <f43fc5580705231228s2a29c802v3d46a78ed65e8972@mail.gmail.com>

On Wednesday 23 May 2007, Blue Swirl wrote:
> On 5/23/07, Paul Brook <paul@codesourcery.com> wrote:
> > 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?
> I made the API change and converted Sparc timers. Looks like it works
> (guest clock runs normally), though there are the following messages
> on startup:
> FIXME: ptimer_set_limit with running timer
>
> Comments? Did I break something?

Code looks reasonable to me.  The FIXME means you're changing the timer 
parameters after starting the timer. I didn't check whether this does 
anything sensible (this may depend on the device), hence the message.
It probably needs some attention when reload == 1 && s->enabled.

Note that save/restore is not implemented.  You may wish to implement this 
before applying your changes.  This doesn't effect the Arm targets because 
they can't save/restore at all.

Paul

  reply	other threads:[~2007-05-23 19:48 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 [this message]
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=200705232048.16793.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 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.