From: Randy Dunlap <rdunlap@infradead.org>
To: Laurent Dufour <ldufour@linux.ibm.com>,
mpe@ellerman.id.au, npiggin@gmail.com,
christophe.leroy@csgroup.eu, wim@linux-watchdog.org,
linux@roeck-us.net, nathanl@linux.ibm.com
Cc: hch@infradead.org, linuxppc-dev@lists.ozlabs.org,
linux-kernel@vger.kernel.org, haren@linux.vnet.ibm.com,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v4 4/4] pseries/mobility: set NMI watchdog factor during LPM
Date: Tue, 12 Jul 2022 09:25:32 -0700 [thread overview]
Message-ID: <a646b2e9-e7a7-3d52-413e-4e2b8c48e383@infradead.org> (raw)
In-Reply-To: <20220712143202.23144-5-ldufour@linux.ibm.com>
Hi--
On 7/12/22 07:32, Laurent Dufour wrote:
> 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
are
> 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,
an NMI
> 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
an LPM. the CPU is
> stopped for the switchover sequence, the NMI watchdog timer is set to
> watchdog_tresh + factor%
watchdog_thresh
>
> 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).
watchdog_thresh
> 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.
an LPM.
>
> Reviewed-by: Nicholas Piggin <npiggin@gmail.com>
> 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).
>
This entire block should be in kernel-parameters.txt, not .rst,
and it should be formatted like everything else in the .txt file.
>
> +nmi_watchdog_factor (PPC only)
> +==================================
> +
> +Factor apply to to the NMI watchdog timeout (only when ``nmi_watchdog`` is
Factor to apply to the NMI
> +set to 1). This factor represents the percentage added to
> +``watchdog_thresh`` when calculating the NMI watchdog timeout during a
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).
> +
> +
> numa_balancing
> ==============
>
--
~Randy
next prev parent reply other threads:[~2022-07-12 16:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-12 14:31 [PATCH v4 0/4] Extending NMI watchdog during LPM Laurent Dufour
2022-07-12 14:31 ` [PATCH v4 1/4] powerpc/mobility: wait for memory transfer to complete Laurent Dufour
2022-07-12 14:32 ` [PATCH v4 2/4] watchdog: export lockup_detector_reconfigure Laurent Dufour
2022-07-12 14:32 ` [PATCH v4 3/4] powerpc/watchdog: introduce a NMI watchdog's factor Laurent Dufour
2022-07-12 14:32 ` [PATCH v4 4/4] pseries/mobility: set NMI watchdog factor during LPM Laurent Dufour
2022-07-12 16:25 ` Randy Dunlap [this message]
2022-07-13 10:56 ` Laurent Dufour
2022-07-13 14:42 ` Randy Dunlap
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=a646b2e9-e7a7-3d52-413e-4e2b8c48e383@infradead.org \
--to=rdunlap@infradead.org \
--cc=christophe.leroy@csgroup.eu \
--cc=haren@linux.vnet.ibm.com \
--cc=hch@infradead.org \
--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=npiggin@gmail.com \
--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;
as well as URLs for NNTP newsgroup(s).