From: Laurent Vivier <lvivier@redhat.com>
To: qemu-devel@nongnu.org
Cc: Paolo Bonzini <pbonzini@redhat.com>,
"Richard W.M. Jones" <rjones@redhat.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: Re: [Qemu-devel] [PATCH] i6300esb: correctly convert watchdog clock ticks into nanoseconds
Date: Mon, 3 Aug 2015 16:28:14 +0200 [thread overview]
Message-ID: <55BF7A7E.1050303@redhat.com> (raw)
In-Reply-To: <1438609948-3744-1-git-send-email-lvivier@redhat.com>
On 03/08/2015 15:52, Laurent Vivier wrote:
> Originally, qemu_mod_timer() was using ticks to count time.
> And i6300esb was converting internal clock ticks (33 MHz) to
> QEMU timer ticks.
>
> The timer has been changed by a script to use nanoseconds:
>
> 7447545 change all other clock references to use
> nanosecond resolution accessors
>
> As i6300esb takes nanoseconds, we don't need anymore to
> multiply counter by get_ticks_per_sec()/33MHz, but instead
> we must convert watchdog ticks into nanoseconds.
>
> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> ---
> hw/watchdog/wdt_i6300esb.c | 25 +++++++++++++++----------
> 1 file changed, 15 insertions(+), 10 deletions(-)
>
> diff --git a/hw/watchdog/wdt_i6300esb.c b/hw/watchdog/wdt_i6300esb.c
> index cfa2b1b..21119ab 100644
> --- a/hw/watchdog/wdt_i6300esb.c
> +++ b/hw/watchdog/wdt_i6300esb.c
> @@ -124,19 +124,24 @@ static void i6300esb_restart_timer(I6300State *d, int stage)
> else
> timeout = d->timer2_preload;
>
> - if (d->clock_scale == CLOCK_SCALE_1KHZ)
> + /* convert timeout to 33Mhz clock ticks */
> + if (d->clock_scale == CLOCK_SCALE_1KHZ) {
> + /* The 20-bit Preload Value is loaded into bits 34:15 of the
> + * main down counter. [...] The approximate clock generated
> + * is 1 KHz, (Default)
> + */
> timeout <<= 15;
> - else
> + } else {
> + /* The 20-bit Preload Value is loaded into bits 24:5 of the
> + * main down counter. [...] The approximate clock generated
> + * is 1 MHz.
> + */
> timeout <<= 5;
> -
> - /* Get the timeout in units of ticks_per_sec.
> - *
> - * ticks_per_sec is typically 10^9 == 0x3B9ACA00 (30 bits), with
> - * 20 bits of user supplied preload, and 15 bits of scale, the
> - * multiply here can exceed 64-bits, before we divide by 33MHz, so
> - * we use a higher-precision intermediate result.
> + }
> + /* A 33 Mhz clock gives a 30 ns tick,
> + * convert timeout from ticks to ns
> */
> - timeout = muldiv64(get_ticks_per_sec(), timeout, 33000000);
> + timeout *= 30;
I'm wondering if a 33 Mhz clock is 33000000 Hz or 33333333 Hz ?
if this is the former, I should use "timeout = timeout * 1000 / 33" instead.
(35 bit value * 10 bit value = 45 bit value, it fits in a 64 bit integer)
Any comment ?
>
> i6300esb_debug("stage %d, timeout %" PRIi64 "\n", d->stage, timeout);
>
>
next prev parent reply other threads:[~2015-08-03 14:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-03 13:52 [Qemu-devel] [PATCH] i6300esb: correctly convert watchdog clock ticks into nanoseconds Laurent Vivier
2015-08-03 14:28 ` Laurent Vivier [this message]
2015-08-03 14:46 ` Richard W.M. Jones
2015-08-03 15:02 ` Paolo Bonzini
2015-08-03 15:13 ` Laurent Vivier
2015-08-03 15:18 ` Paolo Bonzini
2015-08-03 15:35 ` Laurent Vivier
2015-08-03 16:06 ` Paolo Bonzini
2015-08-03 15:06 ` Laurent Vivier
2015-08-04 8:27 ` [Qemu-devel] [PATCH][TRIVIAL] i6300esb: fix timer overflow Laurent Vivier
2015-08-04 13:47 ` Richard W.M. Jones
2015-08-05 0:01 ` David Gibson
2015-09-06 10:29 ` Michael Tokarev
2015-09-06 14:35 ` Paolo Bonzini
2015-09-06 14:41 ` Laurent Vivier
2015-08-04 10:13 ` [Qemu-devel] [PATCH] i6300esb: correctly convert watchdog clock ticks into nanoseconds Richard W.M. Jones
2015-08-04 10:25 ` Laurent Vivier
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=55BF7A7E.1050303@redhat.com \
--to=lvivier@redhat.com \
--cc=david@gibson.dropbear.id.au \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/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).