From: Arthur Mesh <amesh@juniper.net>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Make EFI watchdog behaviour configurable
Date: Fri, 11 Sep 2015 08:57:41 -0700 [thread overview]
Message-ID: <20150911155741.GQ35797@juniper.net> (raw)
In-Reply-To: <55F2F22E.5030304@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1027 bytes --]
On Fri, Sep 11, 2015 at 06:24:30PM +0300, Andrei Borzenkov wrote:
> >> Why is it not enough? You can always add it to your grub.cfg.
> >
> > Well, it still leaves a window of time where the system operates w/o a watchdog.
> > It could be a problem if grub.cfg resides on a network file system, and is not
> > accessible, in which case the system would hang.
>
> I'm fine with making it controlled by parameter passed to grub
> invocation or EFI variable. We discussed parameters several times but
> did not come to definitive conclusion hos interface should look like.
BIOS wouldn't know when to tell GRUB to disable the watchdog. If it did,
BIOS wouldn't have to enable the watchdog to begin with.
EFI variables is a better idea, but unless we have a well defined
interface, it will get unwieldy very quickly..
Can we compromise and simply proceed with the efi-watchdog cli? If so,
I'll gladly submit a new patch.
Thanks
--
Arthur Mesh <amesh@juniper.net>
Juniper Networks
+1 408 936-4968
[-- Attachment #2: Type: application/pgp-signature, Size: 648 bytes --]
prev parent reply other threads:[~2015-09-11 15:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-10 0:11 [PATCH] Make EFI watchdog behaviour configurable Arthur Mesh
2015-09-11 14:32 ` Andrei Borzenkov
2015-09-11 14:53 ` Arthur Mesh
2015-09-11 15:24 ` Andrei Borzenkov
2015-09-11 15:57 ` Arthur Mesh [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=20150911155741.GQ35797@juniper.net \
--to=amesh@juniper.net \
--cc=grub-devel@gnu.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).