All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Jia Liu <proljc@gmail.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	Jason Wang <jasowang@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Leon Alrae <leon.alrae@imgtec.com>
Subject: Re: [Qemu-trivial] [PATCH 0/7] remove useless muldiv64()
Date: Tue, 25 Aug 2015 18:51:08 -0400 (EDT)	[thread overview]
Message-ID: <285075347.18984776.1440543068614.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1440535491-4511-1-git-send-email-lvivier@redhat.com>

> Originally, timers were ticks based, and it made sense to
> add ticks to current time to know when to trigger an alarm.
> 
> But since commit:
> 
> 7447545 change all other clock references to use nanosecond resolution
> accessors
> 
> All timers use nanoseconds and we need to convert ticks to nanoseconds, by
> doing something like:
> 
>      y = muldiv64(x, get_ticks_per_sec(), TIMER_FREQ)
> 
> where x is the number of device ticks and y the number of system ticks.
> 
> y is used as nanoseconds in timer functions,
> it works because 1 tick is 1 nanosecond.
> (get_ticks_per_sec() is 10^9)
> 
> But if get_ticks_per_sec() / TIMER_FREQ is an integer, we can do:
> 
>     y = x * TIMER_PERIOD;

Cc: qemu-trivial@nongnu.org

Paolo


WARNING: multiple messages have this Message-ID (diff)
From: Paolo Bonzini <pbonzini@redhat.com>
To: Laurent Vivier <lvivier@redhat.com>
Cc: Peter Maydell <peter.maydell@linaro.org>,
	Jia Liu <proljc@gmail.com>,
	"Michael S . Tsirkin" <mst@redhat.com>,
	qemu-trivial <qemu-trivial@nongnu.org>,
	Jason Wang <jasowang@redhat.com>,
	qemu-devel@nongnu.org, Stefan Hajnoczi <stefanha@redhat.com>,
	Leon Alrae <leon.alrae@imgtec.com>,
	Aurelien Jarno <aurelien@aurel32.net>
Subject: Re: [Qemu-devel] [PATCH 0/7] remove useless muldiv64()
Date: Tue, 25 Aug 2015 18:51:08 -0400 (EDT)	[thread overview]
Message-ID: <285075347.18984776.1440543068614.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <1440535491-4511-1-git-send-email-lvivier@redhat.com>

> Originally, timers were ticks based, and it made sense to
> add ticks to current time to know when to trigger an alarm.
> 
> But since commit:
> 
> 7447545 change all other clock references to use nanosecond resolution
> accessors
> 
> All timers use nanoseconds and we need to convert ticks to nanoseconds, by
> doing something like:
> 
>      y = muldiv64(x, get_ticks_per_sec(), TIMER_FREQ)
> 
> where x is the number of device ticks and y the number of system ticks.
> 
> y is used as nanoseconds in timer functions,
> it works because 1 tick is 1 nanosecond.
> (get_ticks_per_sec() is 10^9)
> 
> But if get_ticks_per_sec() / TIMER_FREQ is an integer, we can do:
> 
>     y = x * TIMER_PERIOD;

Cc: qemu-trivial@nongnu.org

Paolo

  parent reply	other threads:[~2015-08-25 22:51 UTC|newest]

Thread overview: 12+ 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
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 ` Paolo Bonzini [this message]
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=285075347.18984776.1440543068614.JavaMail.zimbra@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=jasowang@redhat.com \
    --cc=leon.alrae@imgtec.com \
    --cc=lvivier@redhat.com \
    --cc=mst@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=proljc@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@nongnu.org \
    --cc=stefanha@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 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.