[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6232bb4-a8e5-8f33-e80e-06b1356565b7@infradead.org>
Date: Wed, 13 Jul 2022 13:17:29 -0700
From: Randy Dunlap <rdunlap@...radead.org>
To: Laurent Dufour <ldufour@...ux.ibm.com>, mpe@...erman.id.au,
npiggin@...il.com, christophe.leroy@...roup.eu,
wim@...ux-watchdog.org, linux@...ck-us.net, nathanl@...ux.ibm.com
Cc: haren@...ux.vnet.ibm.com, hch@...radead.org,
linux-kernel@...r.kernel.org, linuxppc-dev@...ts.ozlabs.org,
linux-watchdog@...r.kernel.org
Subject: Re: [PATCH v5 4/4] pseries/mobility: set NMI watchdog factor during
an LPM
Hi Laurent,
On 7/13/22 08:47, Laurent Dufour wrote:
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index ddccd1077462..d73faa619c15 100644
> --- a/Documentation/admin-guide/sysctl/kernel.rst
> +++ b/Documentation/admin-guide/sysctl/kernel.rst
> @@ -592,6 +592,18 @@ to the guest kernel command line (see
> Documentation/admin-guide/kernel-parameters.rst).
>
>
> +nmi_wd_lpm_factor (PPC only)
> +============================
> +
> +Factor apply to the NMI watchdog timeout (only when ``nmi_watchdog`` is
Factor to apply to
> +set to 1). This factor represents the percentage added to
> +``watchdog_thresh`` when calculating the NMI watchdog timeout during an
> +LPM. The soft lockup timeout is not impacted.
> +
> +A value of 0 means no change. The default value is 200 meaning the NMI
> +watchdog is set to 30s (based on ``watchdog_thresh`` equal to 10).
--
~Randy
Powered by blists - more mailing lists