From: Nicholas Piggin <npiggin@gmail.com>
To: benh@kernel.crashing.org, haren@linux.vnet.ibm.com,
Laurent Dufour <ldufour@linux.ibm.com>,
linux@roeck-us.net, mpe@ellerman.id.au, nathanl@linux.ibm.com,
paulus@samba.org, wim@linux-watchdog.org
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 4/4] pseries/mobility: set NMI watchdog factor during LPM
Date: Tue, 12 Jul 2022 11:46:33 +1000 [thread overview]
Message-ID: <1657590189.b3s2aqv3sj.astroid@bobo.none> (raw)
In-Reply-To: <20220627135347.32624-5-ldufour@linux.ibm.com>
Excerpts from Laurent Dufour's message of June 27, 2022 11:53 pm:
> During a LPM, while the memory transfer is in progress on the arrival side,
> some latencies is generated when accessing not yet transferred pages on the
> arrival side. Thus, the NMI watchdog may be triggered too frequently, which
> increases the risk to hit a NMI interrupt in a bad place in the kernel,
> leading to a kernel panic.
>
> Disabling the Hard Lockup Watchdog until the memory transfer could be a too
> strong work around, some users would want this timeout to be eventually
> triggered if the system is hanging even during LPM.
>
> Introduce a new sysctl variable nmi_watchdog_factor. It allows to apply
> a factor to the NMI watchdog timeout during a LPM. Just before the CPU are
> stopped for the switchover sequence, the NMI watchdog timer is set to
> watchdog_tresh + factor%
>
> A value of 0 has no effect. The default value is 200, meaning that the NMI
> watchdog is set to 30s during LPM (based on a 10s watchdog_tresh value).
> Once the memory transfer is achieved, the factor is reset to 0.
>
> Setting this value to a high number is like disabling the NMI watchdog
> during a LPM.
>
> Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com>
> ---
> Documentation/admin-guide/sysctl/kernel.rst | 12 ++++++
> arch/powerpc/platforms/pseries/mobility.c | 43 +++++++++++++++++++++
> 2 files changed, 55 insertions(+)
>
> diff --git a/Documentation/admin-guide/sysctl/kernel.rst b/Documentation/admin-guide/sysctl/kernel.rst
> index ddccd1077462..0bb0b7f27e96 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_watchdog_factor (PPC only)
> +==================================
> +
> +Factor apply to to the NMI watchdog timeout (only when ``nmi_watchdog`` is
> +set to 1). This factor represents the percentage added to
> +``watchdog_thresh`` when calculating the NMI watchdog timeout during a
> +LPM. The soft lockup timeout is not impacted.
Could "LPM" or "mobility" be a bit more prominent in the parameter name
and documentation? Something else might want to add a factor as well,
one day.
Otherwise the code looks okay.
Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> +
> +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).
> +
> +
> numa_balancing
> ==============
>
> diff --git a/arch/powerpc/platforms/pseries/mobility.c b/arch/powerpc/platforms/pseries/mobility.c
> index 907a779074d6..649155faafc2 100644
> --- a/arch/powerpc/platforms/pseries/mobility.c
> +++ b/arch/powerpc/platforms/pseries/mobility.c
> @@ -48,6 +48,39 @@ struct update_props_workarea {
> #define MIGRATION_SCOPE (1)
> #define PRRN_SCOPE -2
>
> +#ifdef CONFIG_PPC_WATCHDOG
> +static unsigned int nmi_wd_factor = 200;
> +
> +#ifdef CONFIG_SYSCTL
> +static struct ctl_table nmi_wd_factor_ctl_table[] = {
> + {
> + .procname = "nmi_watchdog_factor",
> + .data = &nmi_wd_factor,
> + .maxlen = sizeof(int),
> + .mode = 0644,
> + .proc_handler = proc_douintvec_minmax,
> + },
> + {}
> +};
> +static struct ctl_table nmi_wd_factor_sysctl_root[] = {
> + {
> + .procname = "kernel",
> + .mode = 0555,
> + .child = nmi_wd_factor_ctl_table,
> + },
> + {}
> +};
> +
> +static int __init register_nmi_wd_factor_sysctl(void)
> +{
> + register_sysctl_table(nmi_wd_factor_sysctl_root);
> +
> + return 0;
> +}
> +device_initcall(register_nmi_wd_factor_sysctl);
> +#endif /* CONFIG_SYSCTL */
> +#endif /* CONFIG_PPC_WATCHDOG */
> +
> static int mobility_rtas_call(int token, char *buf, s32 scope)
> {
> int rc;
> @@ -702,13 +735,20 @@ static int pseries_suspend(u64 handle)
> static int pseries_migrate_partition(u64 handle)
> {
> int ret;
> + unsigned int factor = 0;
>
> +#ifdef CONFIG_PPC_WATCHDOG
> + factor = nmi_wd_factor;
> +#endif
> ret = wait_for_vasi_session_suspending(handle);
> if (ret)
> return ret;
>
> vas_migration_handler(VAS_SUSPEND);
>
> + if (factor)
> + watchdog_nmi_set_lpm_factor(factor);
> +
> ret = pseries_suspend(handle);
> if (ret == 0) {
> post_mobility_fixup();
> @@ -716,6 +756,9 @@ static int pseries_migrate_partition(u64 handle)
> } else
> pseries_cancel_migration(handle, ret);
>
> + if (factor)
> + watchdog_nmi_set_lpm_factor(0);
> +
> vas_migration_handler(VAS_RESUME);
>
> return ret;
> --
> 2.36.1
>
>
next prev parent reply other threads:[~2022-07-12 1:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 13:53 [PATCH v3 0/4] Extending NMI watchdog " Laurent Dufour
2022-06-27 13:53 ` [PATCH v3 1/4] powerpc/mobility: wait for memory transfer to complete Laurent Dufour
2022-07-12 1:33 ` Nicholas Piggin
2022-07-12 9:38 ` Laurent Dufour
2022-06-27 13:53 ` [PATCH v3 2/4] watchdog: export lockup_detector_reconfigure Laurent Dufour
2022-06-27 13:53 ` [PATCH v3 3/4] powerpc/watchdog: introduce a NMI watchdog's factor Laurent Dufour
2022-07-12 1:42 ` Nicholas Piggin
2022-07-12 9:51 ` Laurent Dufour
2022-06-27 13:53 ` [PATCH v3 4/4] pseries/mobility: set NMI watchdog factor during LPM Laurent Dufour
2022-07-12 1:46 ` Nicholas Piggin [this message]
2022-07-12 9:47 ` Laurent Dufour
2022-07-13 14:22 ` Laurent Dufour
2022-07-12 1:21 ` [PATCH v3 0/4] Extending NMI watchdog " Nicholas Piggin
2022-07-12 9:32 ` Laurent Dufour
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=1657590189.b3s2aqv3sj.astroid@bobo.none \
--to=npiggin@gmail.com \
--cc=benh@kernel.crashing.org \
--cc=haren@linux.vnet.ibm.com \
--cc=ldufour@linux.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=nathanl@linux.ibm.com \
--cc=paulus@samba.org \
--cc=wim@linux-watchdog.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
all inboxes | Powered by JetHome®