From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: pavel.dovgaluk@ispras.ru, pbonzini@redhat.com,
"Alex Bennée" <alex.bennee@linaro.org>,
boost.lists@gmail.com, victor.clement@openwide.fr
Subject: [PATCH v1 0/2] clean-ups for sleep=off behaviour
Date: Tue, 28 Jul 2020 15:10:03 +0100 [thread overview]
Message-ID: <20200728141005.28664-1-alex.bennee@linaro.org> (raw)
Hi,
These fixes are more band-aids than anything else but they at least
improve on the original situation where running a zephyr build with:
-icount shift=6,align=off,sleep=off
would lock the monitor hard as time rushed into the future. With these
patches time still runs to the future pretty fast as Zephyr spends
most of it's time in WFI waiting for input with a CVAL far in the
future. This does does raise the question of what sleep=off is even
for?
Alex Bennée (2):
qemu-timer: gracefully handle the end of time
target/arm: only set the nexttick timer if !ISTATUS
include/sysemu/cpus.h | 2 ++
softmmu/cpus.c | 13 +++++++++++++
target/arm/helper.c | 35 ++++++++++++++++++++++-------------
util/qemu-timer.c | 16 ++++++++++++++++
stubs/Makefile.objs | 1 +
5 files changed, 54 insertions(+), 13 deletions(-)
--
2.20.1
next reply other threads:[~2020-07-28 14:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-28 14:10 Alex Bennée [this message]
2020-07-28 14:10 ` [PATCH v1 1/2] qemu-timer: gracefully handle the end of time Alex Bennée
2020-07-28 14:42 ` Paolo Bonzini
2020-07-28 16:08 ` Alex Bennée
2020-07-28 16:58 ` Paolo Bonzini
2020-07-28 14:10 ` [PATCH v1 2/2] target/arm: only set the nexttick timer if !ISTATUS Alex Bennée
2020-07-28 14:16 ` Peter Maydell
2020-07-28 16:11 ` Alex Bennée
2020-07-28 16:23 ` 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=20200728141005.28664-1-alex.bennee@linaro.org \
--to=alex.bennee@linaro.org \
--cc=boost.lists@gmail.com \
--cc=pavel.dovgaluk@ispras.ru \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=victor.clement@openwide.fr \
/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).