From: Andre Przywara <andre.przywara@arm.com>
To: Tom Rini <trini@konsulko.com>
Cc: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>,
u-boot@lists.denx.de, Heinrich Schuchardt <xypron.glpk@gmx.de>,
Alexander Graf <agraf@csgraf.de>
Subject: Re: [PATCH 1/1] efi_loader: stop watchdogs in ExitBootServices()
Date: Tue, 9 Nov 2021 21:47:06 +0000 [thread overview]
Message-ID: <20211109214706.579ddb1e@slackpad.fritz.box> (raw)
In-Reply-To: <20211109181828.GX24579@bill-the-cat>
On Tue, 9 Nov 2021 13:18:28 -0500
Tom Rini <trini@konsulko.com> wrote:
> On Tue, Nov 09, 2021 at 07:15:10PM +0100, Heinrich Schuchardt wrote:
> > On 11/9/21 18:55, Tom Rini wrote:
> > > On Tue, Nov 09, 2021 at 11:19:01AM +0100, Heinrich Schuchardt wrote:
> > >
> > > > The UEFI specification requires for ExitBootServices() that "the boot
> > > > services watchdog timer is disabled". We already disable the software
> > > > watchdog. We should additionally disable the hardware watchdogs.
> > > >
> > > > Reported-by: Andre Przywara <andre.przywara@arm.com>
> > > > Signed-off-by: Heinrich Schuchardt <heinrich.schuchardt@canonical.com>
> > >
> > > Let me start by saying thank you for bringing this up with UEFI folks as
> > > well. To be clear, for right now I would much rather see U-Boot
> > > continue to be non-complaint with UEFI in this regard and assume that a
> > > running watchdog will be able to be handled by the running OS (which
> > > tends to be the case, but not always as sunxi has just shown) than to
> > > attempt to be complaint with the spec as it stands now as I am hopeful
> > > that we can get this case handled in a way that matches long standing
> > > industry practice.
> > >
> >
> > We have either merge this patch or
> >
> > [1/1] watchdog: don't autostart watchdog on Sunxi boards
> > https://patchwork.ozlabs.org/project/uboot/patch/20211105183431.117221-1-heinrich.schuchardt@canonical.com/
> >
> > or we will be breaking boot processes that have been running up to now.
> >
> > As Sunxi watchdogs were only enabled by a recent patch disabling autostart
> > should not cause any harm.
>
> Yes, I was expecting a PR from Andre in my inbox this morning with your
This was my plan as well, until I opened up the UEFI spec ;-)
Also I didn't see any problems so far in my - admittedly limited -
casual testing (because I boot quickly and have the WDT compiled in).
But I see it now when disabling the watchdog in the kernel, so will
take the "don't autostart" patch anyway.
If people have an embedded deployment where they rely on the watchdog,
they can surely enable it before building U-Boot.
Cheers,
Andre
> patch, as he had said he would apply it. I'm just assuming now I got a
> bit ahead of myself with expecting it so quickly.
>
next prev parent reply other threads:[~2021-11-09 21:48 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 10:19 [PATCH 1/1] efi_loader: stop watchdogs in ExitBootServices() Heinrich Schuchardt
2021-11-09 10:19 ` Heinrich Schuchardt
2021-11-09 14:20 ` Michael Walle
2021-11-09 14:46 ` Mark Kettenis
2021-11-09 14:54 ` Michael Walle
2021-11-09 17:30 ` Heinrich Schuchardt
2021-11-09 17:55 ` Tom Rini
2021-11-09 18:15 ` Heinrich Schuchardt
2021-11-09 18:18 ` Tom Rini
2021-11-09 21:47 ` Andre Przywara [this message]
2021-11-09 23:45 ` Grant Likely
-- strict thread matches above, loose matches on Subject: below --
2023-01-28 8:57 Heinrich Schuchardt
2023-01-30 18:13 ` Tom Rini
2023-01-30 18:30 ` Tom Rini
2023-01-31 12:03 ` Ilias Apalodimas
2023-01-31 14:16 ` Simon Glass
2023-01-31 14:48 ` Heinrich Schuchardt
2023-01-31 15:07 ` Tom Rini
2023-02-01 8:32 ` Rasmus Villemoes
2023-02-01 9:00 ` Heinrich Schuchardt
2023-02-02 8:17 ` Etienne Carriere
2023-02-02 17:12 ` Simon Glass
2023-02-02 17:22 ` Tom Rini
2023-02-03 2:15 ` Simon Glass
2023-02-03 7:30 ` Rasmus Villemoes
2023-02-07 14:59 ` Michael Walle
2023-02-07 15:08 ` Heinrich Schuchardt
2023-02-07 15:29 ` Michael Walle
2023-02-07 15:30 ` Heinrich Schuchardt
2023-02-07 15:34 ` Michael Walle
2023-02-03 15:51 ` Tom Rini
2023-02-04 0:20 ` Simon Glass
2023-02-01 12:49 ` Mark Kettenis
2023-02-01 15:21 ` Tom Rini
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=20211109214706.579ddb1e@slackpad.fritz.box \
--to=andre.przywara@arm.com \
--cc=agraf@csgraf.de \
--cc=heinrich.schuchardt@canonical.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=xypron.glpk@gmx.de \
/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