From: Thomas Huth <thuth@redhat.com>
To: Ilya Leoshkevich <iii@linux.ibm.com>,
Richard Henderson <richard.henderson@linaro.org>,
David Hildenbrand <david@redhat.com>
Cc: qemu-s390x@nongnu.org, qemu-devel@nongnu.org, qemu-stable@nongnu.org
Subject: Re: [PATCH v4 1/4] target/s390x: Fix missing interrupts for small CKC values
Date: Thu, 27 Nov 2025 17:43:21 +0100 [thread overview]
Message-ID: <a0accce9-6042-4a7b-a7c7-218212818891@redhat.com> (raw)
In-Reply-To: <20251016175954.41153-2-iii@linux.ibm.com>
On 16/10/2025 19.58, Ilya Leoshkevich wrote:
> Suppose TOD clock value is 0x1111111111111111 and clock-comparator
> value is 0, in which case clock-comparator interruption should occur
> immediately.
>
> With the current code, tod2time(env->ckc - td->base.low) ends up being
> a very large number, so this interruption never happens.
>
> Fix by firing the timer immediately if env->ckc < td->base.low.
>
> Cc: qemu-stable@nongnu.org
> Reviewed-by: Thomas Huth <thuth@redhat.com>
> Signed-off-by: Ilya Leoshkevich <iii@linux.ibm.com>
> ---
Hi Ilya,
this patch unfortunately broke reverse debugging on the s390x target.
Something like this used to work before:
qemu-img create -f qcow2 /tmp/disk.qcow2 2G
./qemu-system-s390x -nographic \
-icount shift=6,rr=record,rrfile=replay.bin,rrsnapshot=init \
-net none -drive file=/tmp/disk.qcow2,if=none
./qemu-system-s390x -nographic \
-icount shift=6,rr=replay,rrfile=replay.bin,rrsnapshot=init \
-net none -drive file=/tmp/disk.qcow2,if=none
With this commit and later, the replay hangs somewhere in an endless loop.
Do you have any ideas what could go wrong here?
Thanks,
Thomas
> diff --git a/target/s390x/tcg/misc_helper.c b/target/s390x/tcg/misc_helper.c
> index 6d9d601d29a..215b5b9d933 100644
> --- a/target/s390x/tcg/misc_helper.c
> +++ b/target/s390x/tcg/misc_helper.c
> @@ -199,11 +199,15 @@ static void update_ckc_timer(CPUS390XState *env)
> return;
> }
>
> - /* difference between origins */
> - time = env->ckc - td->base.low;
> + if (env->ckc < td->base.low) {
> + time = 0;
> + } else {
> + /* difference between origins */
> + time = env->ckc - td->base.low;
>
> - /* nanoseconds */
> - time = tod2time(time);
> + /* nanoseconds */
> + time = tod2time(time);
> + }
>
> timer_mod(env->tod_timer, time);
> }
next prev parent reply other threads:[~2025-11-27 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-16 17:58 [PATCH v4 0/3] target/s390x: Fix missing clock-comparator interrupts Ilya Leoshkevich
2025-10-16 17:58 ` [PATCH v4 1/4] target/s390x: Fix missing interrupts for small CKC values Ilya Leoshkevich
2025-11-27 16:43 ` Thomas Huth [this message]
2025-11-27 18:00 ` Ilya Leoshkevich
2025-11-27 21:54 ` Ilya Leoshkevich
2025-10-16 17:58 ` [PATCH v4 2/4] target/s390x: Fix missing clock-comparator interrupts after reset Ilya Leoshkevich
2025-10-16 17:58 ` [PATCH v4 3/4] target/s390x: Use address generation for register branch targets Ilya Leoshkevich
2025-10-16 18:13 ` Thomas Weißschuh
2025-10-16 17:58 ` [PATCH v4 4/4] tests/tcg/s390x: Test SET CLOCK COMPARATOR Ilya Leoshkevich
2025-10-29 9:55 ` [PATCH PING v4 0/3] target/s390x: Fix missing clock-comparator interrupts Ilya Leoshkevich
2025-10-29 12:19 ` Thomas Huth
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=a0accce9-6042-4a7b-a7c7-218212818891@redhat.com \
--to=thuth@redhat.com \
--cc=david@redhat.com \
--cc=iii@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=richard.henderson@linaro.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).