From: Dmitry Osipenko <digetx@gmail.com>
To: QEMU Developers <qemu-devel@nongnu.org>
Cc: Peter Maydell <peter.maydell@linaro.org>,
Peter Crosthwaite <crosthwaitepeter@gmail.com>
Subject: [Qemu-devel] [PATCH v6 0/2] PTimer fix and ARM MPTimer conversion
Date: Fri, 23 Oct 2015 23:03:54 +0300 [thread overview]
Message-ID: <cover.1445627810.git.digetx@gmail.com> (raw)
Changelog for ARM MPTimer QEMUTimer to ptimer conversion:
V2: Fixed changing periodic timer counter value "on the fly". I added a
test to the gist to cover that issue.
V3: Fixed starting the timer with load = 0 and counter != 0, added tests
to the gist for this issue. Changed vmstate version for all VMSD's,
since loadvm doesn't check version of nested VMSD.
V4: Fixed spurious IT bit set for the timer starting in the periodic mode
with counter = 0. Test added.
V5: Code cleanup, now depends on ptimer_set_limit() fix.
V6: No code change, added test to check ptimer_get_count() with corrected
.limit value.
ARM MPTimer tests: https://gist.github.com/digetx/dbd46109503b1a91941a
Patch for ptimer is introduced since V5 of ARM MPTimer conversion.
Changelog for ptimer patch:
V5: Only fixed ptimer_set_limit() for the disabled timer.
V6: As was pointed by Peter Maydell there are other issues beyond
ptimer_set_limit(), so V6 supposed to cover all those issues.
Dmitry Osipenko (2):
hw/ptimer: Fix issues caused by artificially limited timer timeout
arm_mptimer: Convert to use ptimer
hw/core/ptimer.c | 36 ++++++++------
hw/timer/arm_mptimer.c | 110 ++++++++++++++++++-----------------------
include/hw/timer/arm_mptimer.h | 4 +-
3 files changed, 71 insertions(+), 79 deletions(-)
--
2.6.1
next reply other threads:[~2015-10-23 20:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 20:03 Dmitry Osipenko [this message]
2015-10-23 20:03 ` [Qemu-devel] [PATCH v6 1/2] hw/ptimer: Fix issues caused by artificially limited timer timeout Dmitry Osipenko
2015-10-23 20:03 ` [Qemu-devel] [PATCH v6 2/2] arm_mptimer: Convert to use ptimer Dmitry Osipenko
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=cover.1445627810.git.digetx@gmail.com \
--to=digetx@gmail.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).