From: Igor Mammedov <imammedo@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, leif.lindholm@oss.qualcomm.com,
eauger@redhat.com
Subject: [PATCH 0/6] sbsa-gwdt cleanup and fixes
Date: Wed, 2 Sep 2026 14:26:40 +0200 [thread overview]
Message-ID: <20260902122646.2848464-1-imammedo@redhat.com> (raw)
Series picks up dropped gwdt fixes from
[PATCH v3 00/17] Add watchdog support to arm/virt board
https://patchew.org/QEMU/20260624102830.1355552-1-imammedo@redhat.com/
patches were basically rewritten to make changes simpler/easier to reson about.
patch 6/6 is partial fix with open question:
sbsa-gwdt currently mantains WVC in since VM start ticks, which works fine under
TCG. However under KVM those system counter domains diverge and CNTPCT in guest
starts to return host's value. As result WCV reads/writes got mixed up with
QEMU still assuming VM timeframe while guest using host's one.
Question is how should we fix it?
Igor Mammedov (6):
sbsa-gwdt: reduce code ident
arm: gwdt: consolidate clear WS0 and WS1 on explicit refresh
arm: gwdt: simplify WCV update condition
sbsa-gwdt: rename sbsa_gwdt_update_timer() to
sbsa_gwdt_wor_update_timer()
sbsa-gwdt: don't arm timer for compare values above INT64_MAX
sbsa-gwdt: reschedule timer on direct WCV load
hw/watchdog/sbsa_gwdt.c | 81 +++++++++++++++++++++++++++--------------
1 file changed, 54 insertions(+), 27 deletions(-)
--
2.52.0
next reply other threads:[~2026-09-02 12:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 12:26 Igor Mammedov [this message]
2026-09-02 12:26 ` [PATCH 1/6] sbsa-gwdt: reduce code ident Igor Mammedov
2026-09-08 14:28 ` Peter Maydell
2026-09-08 14:47 ` Igor Mammedov
2026-09-02 12:26 ` [PATCH 2/6] arm: gwdt: consolidate clear WS0 and WS1 on explicit refresh Igor Mammedov
2026-09-08 14:34 ` Peter Maydell
2026-09-02 12:26 ` [PATCH 3/6] arm: gwdt: simplify WCV update condition Igor Mammedov
2026-09-08 14:49 ` Peter Maydell
2026-09-02 12:26 ` [PATCH 4/6] sbsa-gwdt: rename sbsa_gwdt_update_timer() to sbsa_gwdt_wor_update_timer() Igor Mammedov
2026-09-08 14:56 ` Peter Maydell
2026-09-02 12:26 ` [PATCH 5/6] sbsa-gwdt: don't arm timer for compare values above INT64_MAX Igor Mammedov
2026-09-08 14:57 ` Peter Maydell
2026-09-02 12:26 ` [PATCH 6/6] sbsa-gwdt: reschedule timer on direct WCV load Igor Mammedov
2026-09-08 14:57 ` Peter Maydell
2026-09-08 15:08 ` [PATCH 0/6] sbsa-gwdt cleanup and fixes Peter Maydell
2026-09-09 8:17 ` Igor Mammedov
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=20260902122646.2848464-1-imammedo@redhat.com \
--to=imammedo@redhat.com \
--cc=eauger@redhat.com \
--cc=leif.lindholm@oss.qualcomm.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 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.