From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Laurent Vivier <lvivier@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
Ani Sinha <ani@anisinha.ca>, Igor Mammedov <imammedo@redhat.com>,
Thomas Huth <thuth@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Eduardo Habkost <eduardo@habkost.net>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
"Richard W.M. Jones" <rjones@redhat.com>
Subject: Re: [PATCH 0/4] hw: make TCO watchdog actually work by default for Q35
Date: Thu, 10 Nov 2022 11:30:45 -0500 [thread overview]
Message-ID: <20221110112956-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20221031131934.425448-1-berrange@redhat.com>
On Mon, Oct 31, 2022 at 01:19:30PM +0000, Daniel P. Berrangé wrote:
> The TCO watchdog is unconditionally integrated into the Q35 machine
> type by default, but at the same time is unconditionally disabled
> from firing by a host config option that overrides guest OS attempts
> to enable it. People have to know to set a magic -global to make
> it non-broken
>
> IOW we're exposing a broken watchdog by default to all Q35 machines,
> but which to the guest OS & its apps looks fully functional :-(
>
> This behaviour was set in response to feedback from Michael:
>
> https://lists.gnu.org/archive/html/qemu-devel/2015-06/msg07128.html
>
> "I think sample high is a safer default."
>
> but as explained in the commit message in the last patch, I think the
> watchdog defaults were already safe without that pin strap setting.
> The guest OS needs to take explicit action to clear the guest visible
> 'no reboot' flag, and so we don't need a second guest hidden 'no reboot'
> flag to override that choice IMHO. Am I missing something ?
>
> NB, I'm toggling this for 7.2 machine type since that's the current
> git latest machine. Since this has already been "broken" for 7 years
> though, I am ambivalent about whether we try todo this for 7.2, vs
> just wait until the 8.0 machine types arrive.
So I expect v2 with minor issues fixed and hopefully a
fixed property (we can debate removing it down the road
if we want).
> Daniel P. Berrangé (4):
> hw/acpi: add trace events for TCO watchdog register access
> hw/isa: add trace events for ICH9 LPC chip config access
> hw/watchdog: add trace events for watchdog action handling
> hw/isa: enable TCO watchdog reboot pin strap by default
>
> hw/acpi/tco.c | 41 +++++++++++++++++++++++++++-------------
> hw/acpi/trace-events | 2 ++
> hw/i386/pc.c | 4 +++-
> hw/isa/lpc_ich9.c | 5 ++++-
> hw/isa/trace-events | 4 ++++
> hw/watchdog/trace-events | 4 ++++
> hw/watchdog/watchdog.c | 4 ++++
> tests/qtest/tco-test.c | 2 +-
> 8 files changed, 50 insertions(+), 16 deletions(-)
>
> --
> 2.37.3
prev parent reply other threads:[~2022-11-10 16:31 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-31 13:19 [PATCH 0/4] hw: make TCO watchdog actually work by default for Q35 Daniel P. Berrangé
2022-10-31 13:19 ` [PATCH 1/4] hw/acpi: add trace events for TCO watchdog register access Daniel P. Berrangé
2022-10-31 13:34 ` Richard W.M. Jones
2022-10-31 13:19 ` [PATCH 2/4] hw/isa: add trace events for ICH9 LPC chip config access Daniel P. Berrangé
2022-10-31 13:36 ` Richard W.M. Jones
2022-10-31 13:19 ` [PATCH 3/4] hw/watchdog: add trace events for watchdog action handling Daniel P. Berrangé
2022-10-31 13:36 ` Richard W.M. Jones
2022-10-31 15:46 ` Philippe Mathieu-Daudé
2022-10-31 13:19 ` [PATCH 4/4] hw/isa: enable TCO watchdog reboot pin strap by default Daniel P. Berrangé
2022-10-31 13:40 ` Richard W.M. Jones
2022-10-31 13:50 ` [PATCH 0/4] hw: make TCO watchdog actually work by default for Q35 Daniel P. Berrangé
2022-10-31 15:48 ` Michael S. Tsirkin
2022-11-01 12:57 ` Igor Mammedov
2022-11-01 13:03 ` Daniel P. Berrangé
2022-11-10 16:29 ` Michael S. Tsirkin
2022-11-10 18:21 ` Daniel P. Berrangé
2022-11-10 16:30 ` Michael S. Tsirkin [this message]
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=20221110112956-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=ani@anisinha.ca \
--cc=berrange@redhat.com \
--cc=eduardo@habkost.net \
--cc=imammedo@redhat.com \
--cc=lvivier@redhat.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=rjones@redhat.com \
--cc=thuth@redhat.com \
/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.