From: "andrzej zaborowski" <balrog@zabor.org>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] add a simple 24mhz clock for the versatile
Date: Sat, 31 Mar 2007 01:39:20 +0200 [thread overview]
Message-ID: <fb249edb0703301639o29ad805cn83653fcede0280e2@mail.gmail.com> (raw)
In-Reply-To: <7ED098B05D69FE41B380586BF1474DBA22D651@ala-mail08.corp.ad.wrs.com>
On 31/03/07, Wessel, Jason <jason.wessel@windriver.com> wrote:
>
>
> uint64_t now = qemu_get_clock(vm_clock);
> return (uint32_t)((now*3)/125);
>
> The optimizer should fix this up with no floating point ops.
Adding to the bikeshed discussion (www.bikeshed.com) this is still not
correct as vm_clock is to be used with ticks_per_sec.
return muldiv64(qemu_get_clock(vm_clock), 24000000, ticks_per_sec);
Regards,
Andrzej
prev parent reply other threads:[~2007-03-30 23:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 16:48 [Qemu-devel] [PATCH] add a simple 24mhz clock for the versatile Jason Wessel
2007-03-30 17:28 ` Paul Brook
2007-03-30 17:49 ` Jonathan Kalbfeld
2007-03-30 23:30 ` Wessel, Jason
2007-03-30 23:39 ` andrzej zaborowski [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=fb249edb0703301639o29ad805cn83653fcede0280e2@mail.gmail.com \
--to=balrog@zabor.org \
--cc=balrogg@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).