From: Abhiram Tilak <atp.exp@gmail.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org, clg@kaod.org,
david@gibson.dropbear.id.au, harshpb@linux.ibm.com,
Abhiram Tilak <atp.exp@gmail.com>
Subject: [PATCH 0/3] Misc: Make watchdog devices using qemu_system_reset_request() use watchdog_perfom_action()
Date: Fri, 16 Feb 2024 19:21:36 +0530 [thread overview]
Message-ID: <20240216135137.8668-3-atp.exp@gmail.com> (raw)
A few watchdog devices use qemu_system_reset_request(). This is not ideal since
behaviour of watchdog-expiry can't be changed by QMP using `watchdog_action`.
As stated in BiteSizedTasks wiki page, instead of using qemu_system_reset_request()
to reset when a watchdog timer expires, let watchdog_perform_action() decide
what to do.
I am unsure about the changes in `spapr_watchdog.c` in patch 3, it would be great
if any of the maintainers review it.
Abhiram Tilak (3):
misc: m48t59: replace qemu_system_reset_request() call with
watchdog_perform_action()
misc: pxa2xx_timer: replace qemu_system_reset_request() call with
watchdog_perform_action()
misc: ppc/spapr: replace qemu_system_reset_request() calls with
watchdog_perform_action()
hw/rtc/m48t59.c | 4 ++--
hw/timer/pxa2xx_timer.c | 3 ++-
hw/watchdog/spapr_watchdog.c | 3 ++-
3 files changed, 6 insertions(+), 4 deletions(-)
--
2.42.1
next reply other threads:[~2024-02-16 13:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-16 13:51 Abhiram Tilak [this message]
2024-02-16 13:51 ` [PATCH 1/3] misc: m48t59: replace qemu_system_reset_request() call with watchdog_perform_action() Abhiram Tilak
2024-02-16 14:49 ` Peter Maydell
2024-02-16 18:27 ` atp exp
2024-02-16 13:51 ` [PATCH 2/3] misc: pxa2xx_timer: " Abhiram Tilak
2024-02-16 14:50 ` Peter Maydell
2024-02-16 13:51 ` [PATCH 3/3] misc: ppc/spapr: replace qemu_system_reset_request() calls " Abhiram Tilak
2024-02-16 14:54 ` Peter Maydell
2024-02-16 18:03 ` atp exp
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=20240216135137.8668-3-atp.exp@gmail.com \
--to=atp.exp@gmail.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=harshpb@linux.ibm.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).