qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: Peter Crosthwaite <crosthwaitepeter@gmail.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	"qemu-devel@nongnu.org Developers" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PATCH 4/7] arm: remove muldiv64()
Date: Tue, 25 Aug 2015 23:36:01 +0200	[thread overview]
Message-ID: <55DCDFC1.2060703@redhat.com> (raw)
In-Reply-To: <CAPokK=rx=+T-QSA8b_AmrBxu=ZYXPijEp4U6aybG8kOsSA1FrQ@mail.gmail.com>



On 25/08/2015 23:11, Peter Crosthwaite wrote:
> On Tue, Aug 25, 2015 at 1:44 PM, Laurent Vivier <lvivier@redhat.com> wrote:
>> muldiv64() is used to convert microseconds to nanoseconds.
>>
>> Use qemu_clock_get_ns() instead of qemu_clock_get_us()
>> to avoid this operation.
>>
>> Signed-off-by: Laurent Vivier <lvivier@redhat.com>
>> ---
>>  target-arm/helper.c | 9 +++------
>>  1 file changed, 3 insertions(+), 6 deletions(-)
>>
>> diff --git a/target-arm/helper.c b/target-arm/helper.c
>> index 1568aa6..f5e8fd8 100644
>> --- a/target-arm/helper.c
>> +++ b/target-arm/helper.c
>> @@ -678,8 +678,7 @@ 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 = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
>>
>>      if (env->cp15.c9_pmcr & PMCRD) {
>>          /* Increment once every 64 processor clock cycles */
>> @@ -717,8 +716,7 @@ 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 = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
>>
> 
> The long term goal here was to replace get_ticks_per_sec with a
> parameterizable CPU frequency so ideally the math should remain. The
> ARM CPU frequency == get_ticks_per_sec is the bigger issue.

OK, I will remove this one from the series.

Perhaps a comment in the original functions would help to understand
what we are doing here...

or something like that:

#define ARM_CPU_FREQ 1000000000 /* FIXME: should be parameterizable */
#define NSEC_PER_SEC 1000000000

total_ticks = muldiv64(qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL),
ARM_CPU_FREQ, NSEC_PER_SEC);

Laurent
> Regards,
> Peter
> 
>>      if (env->cp15.c9_pmcr & PMCRD) {
>>          /* Increment once every 64 processor clock cycles */
>> @@ -738,8 +736,7 @@ 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 = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
>>
>>      if (env->cp15.c9_pmcr & PMCRD) {
>>          /* Increment once every 64 processor clock cycles */
>> --
>> 2.1.0
>>
>>

  reply	other threads:[~2015-08-25 21:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-25 20:44 [Qemu-devel] [PATCH 0/7] remove useless muldiv64() Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 1/7] PCI: remove muldiv64() Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 2/7] mips: " Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 3/7] openrisc: " Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 4/7] arm: " Laurent Vivier
2015-08-25 21:11   ` Peter Crosthwaite
2015-08-25 21:36     ` Laurent Vivier [this message]
2015-08-25 20:44 ` [Qemu-devel] [PATCH 5/7] hpet: " Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 6/7] bt: " Laurent Vivier
2015-08-25 20:44 ` [Qemu-devel] [PATCH 7/7] net: " Laurent Vivier
2015-08-25 22:51 ` [Qemu-devel] [PATCH 0/7] remove useless muldiv64() Paolo Bonzini

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=55DCDFC1.2060703@redhat.com \
    --to=lvivier@redhat.com \
    --cc=crosthwaitepeter@gmail.com \
    --cc=peter.maydell@linaro.org \
    --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).