From: Laurent Vivier <lvivier@redhat.com>
To: pbonzini@redhat.com
Cc: Laurent Vivier <lvivier@redhat.com>, qemu-devel@nongnu.org
Subject: [Qemu-devel] [PULL 6/9] arm: clarify the use of muldiv64()
Date: Fri, 25 Sep 2015 16:09:07 +0200 [thread overview]
Message-ID: <1443190150-17312-7-git-send-email-lvivier@redhat.com> (raw)
In-Reply-To: <1443190150-17312-1-git-send-email-lvivier@redhat.com>
muldiv64() is used to convert microseconds into CPU ticks.
But it is not clear and not commented. This patch uses macro
to clearly identify what is used: time, CPU frequency and ticks.
For an elapsed time and a given frequency, we compute how many ticks
we have.
Signed-off-by: Laurent Vivier <lvivier@redhat.com>
Reviewed-by: Peter Crosthwaite <crosthwaite.peter@gmail.com>
Acked-by: Peter Maydell <peter.maydell@linaro.org>
---
target-arm/helper.c | 14 ++++++++------
1 file changed, 8 insertions(+), 6 deletions(-)
diff --git a/target-arm/helper.c b/target-arm/helper.c
index 12ea88f..8367997 100644
--- a/target-arm/helper.c
+++ b/target-arm/helper.c
@@ -12,6 +12,8 @@
#include <zlib.h> /* For crc32 */
#include "exec/semihost.h"
+#define ARM_CPU_FREQ 1000000000 /* FIXME: 1 GHz, should be configurable */
+
#ifndef CONFIG_USER_ONLY
static inline bool get_phys_addr(CPUARMState *env, target_ulong address,
int access_type, ARMMMUIdx mmu_idx,
@@ -706,8 +708,8 @@ void pmccntr_sync(CPUARMState *env)
{
uint64_t temp_ticks;
- temp_ticks = muldiv64(qemu_clock_get_us(QEMU_CLOCK_VIRTUAL),
- get_ticks_per_sec(), 1000000);
+ temp_ticks = muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
+ ARM_CPU_FREQ, NANOSECONDS_PER_SECOND);
if (env->cp15.c9_pmcr & PMCRD) {
/* Increment once every 64 processor clock cycles */
@@ -745,8 +747,8 @@ static uint64_t pmccntr_read(CPUARMState *env, const ARMCPRegInfo *ri)
return env->cp15.c15_ccnt;
}
- total_ticks = muldiv64(qemu_clock_get_us(QEMU_CLOCK_VIRTUAL),
- get_ticks_per_sec(), 1000000);
+ total_ticks = muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
+ ARM_CPU_FREQ, NANOSECONDS_PER_SECOND);
if (env->cp15.c9_pmcr & PMCRD) {
/* Increment once every 64 processor clock cycles */
@@ -766,8 +768,8 @@ static void pmccntr_write(CPUARMState *env, const ARMCPRegInfo *ri,
return;
}
- total_ticks = muldiv64(qemu_clock_get_us(QEMU_CLOCK_VIRTUAL),
- get_ticks_per_sec(), 1000000);
+ total_ticks = muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
+ ARM_CPU_FREQ, NANOSECONDS_PER_SECOND);
if (env->cp15.c9_pmcr & PMCRD) {
/* Increment once every 64 processor clock cycles */
--
2.1.0
next prev parent reply other threads:[~2015-09-25 15:06 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-25 14:09 [Qemu-devel] [PULL 0/9] muldiv64 queue Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 1/9] i6300esb: remove muldiv64() Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 2/9] rtl8139: " Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 3/9] pcnet: " Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 4/9] mips: " Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 5/9] openrisc: " Laurent Vivier
2015-09-25 14:09 ` Laurent Vivier [this message]
2015-09-25 14:09 ` [Qemu-devel] [PULL 7/9] hpet: " Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 8/9] bt: " Laurent Vivier
2015-09-25 14:09 ` [Qemu-devel] [PULL 9/9] net: " Laurent Vivier
2015-09-25 18:01 ` [Qemu-devel] [PULL 0/9] muldiv64 queue Peter Maydell
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=1443190150-17312-7-git-send-email-lvivier@redhat.com \
--to=lvivier@redhat.com \
--cc=pbonzini@redhat.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).