From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] Make EFI watchdog behaviour configurable
Date: Fri, 11 Sep 2015 18:24:30 +0300 [thread overview]
Message-ID: <55F2F22E.5030304@gmail.com> (raw)
In-Reply-To: <0A811914-E6BD-4AB7-B096-D9C1C8F405CE@juniper.net>
11.09.2015 17:53, Arthur Mesh пишет:
>
>
>
>
>
> On 9/11/15, 7:32 AM, "grub-devel-bounces+amesh=juniper.net@gnu.org on behalf of Andrei Borzenkov" <grub-devel-bounces+amesh=juniper.net@gnu.org on behalf of arvidjaar@gmail.com> wrote:
>
>> 10.09.2015 03:11, Arthur Mesh пишет:
>>> Add `--enable-efi-watchdog' configure argument, which defaults to Off.
>>> When enabled, efi watchdog will not be disabled.
>>> Otherwise, efi watchdog will be disabled.
>>>
>>
>> Please, no. This will result in incompatible binaries without any
>> indication at run-time that allows to distinguish between them.
>
> That's true, but I see no way around that w/o avoiding the initial call to
> disable the watchdog in the efi init routine (and Vladimir is against that idea).
>
>>
>>> Create a command line interface to enable/disable watchdog:
>>> efi-watchdog (enable|disable) <timeout>
>>
>> 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.
next prev parent reply other threads:[~2015-09-11 15:24 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 [this message]
2015-09-11 15:57 ` Arthur Mesh
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=55F2F22E.5030304@gmail.com \
--to=arvidjaar@gmail.com \
--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).