From: Dmitry Osipenko <digetx@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>, qemu-arm@nongnu.org
Cc: Peter Crosthwaite <crosthwaitepeter@gmail.com>,
Peter Maydell <peter.maydell@linaro.org>
Subject: [Qemu-devel] [PATCH v13 7/8] hw/ptimer: Fix counter - 1 returned by ptimer_get_count for the active timer
Date: Fri, 27 May 2016 20:03:35 +0300 [thread overview]
Message-ID: <46f79ce4f464c423bdd5d2b218702854808e3778.1464367869.git.digetx@gmail.com> (raw)
In-Reply-To: <cover.1464367869.git.digetx@gmail.com>
In-Reply-To: <cover.1464367869.git.digetx@gmail.com>
Due to rounding down performed by ptimer_get_count, it returns counter - 1 for
the active timer. That's incorrect because counter should decrement only after
period been expired, not before. I.e. if running timer has been loaded with
value X, then timer counter should stay with X until period expired and
decrement after. Fix this by adding 1 to the counter value for the active and
unexpired timer.
Signed-off-by: Dmitry Osipenko <digetx@gmail.com>
---
hw/core/ptimer.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/hw/core/ptimer.c b/hw/core/ptimer.c
index 9bc70f5..c9f2604 100644
--- a/hw/core/ptimer.c
+++ b/hw/core/ptimer.c
@@ -89,10 +89,10 @@ static void ptimer_tick(void *opaque)
uint64_t ptimer_get_count(ptimer_state *s)
{
+ int64_t now = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
uint64_t counter;
- if (s->enabled && s->delta != 0) {
- int64_t now = qemu_clock_get_ns(QEMU_CLOCK_VIRTUAL);
+ if (s->enabled && s->delta != 0 && now != s->last_event) {
int64_t next = s->next_event;
bool expired = (now - next >= 0);
bool oneshot = (s->enabled == 2);
@@ -144,7 +144,7 @@ uint64_t ptimer_get_count(ptimer_state *s)
if ((uint32_t)(period_frac << shift))
div += 1;
}
- counter = rem / div;
+ counter = rem / div + (expired ? 0 : 1);
if (expired && counter != 0) {
/* Wrap around periodic counter. */
--
2.8.3
next prev parent reply other threads:[~2016-05-27 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-27 17:03 [Qemu-devel] [PATCH v13 0/8] PTimer fixes/features and ARM MPTimer conversion Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 1/8] hw/ptimer: Fix issues caused by the adjusted timer limit value Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 2/8] hw/ptimer: Perform counter wrap around if timer already expired Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 3/8] hw/ptimer: Update .delta on period/freq change Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 4/8] hw/ptimer: Support "on the fly" timer mode switch Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 5/8] hw/ptimer: Introduce ptimer_get_limit Dmitry Osipenko
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 6/8] hw/ptimer: Support running with counter = 0 by introducing new policy feature Dmitry Osipenko
2016-05-28 14:12 ` Dmitry Osipenko
2016-06-06 10:09 ` Peter Maydell
2016-06-06 17:24 ` Dmitry Osipenko
2016-05-27 17:03 ` Dmitry Osipenko [this message]
2016-05-27 17:03 ` [Qemu-devel] [PATCH v13 8/8] arm_mptimer: Convert to use ptimer Dmitry Osipenko
2016-06-06 13:43 ` [Qemu-devel] [PATCH v13 0/8] PTimer fixes/features and ARM MPTimer conversion 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=46f79ce4f464c423bdd5d2b218702854808e3778.1464367869.git.digetx@gmail.com \
--to=digetx@gmail.com \
--cc=crosthwaitepeter@gmail.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.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).