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: linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v3 0/4] Extending NMI watchdog during LPM
Date: Tue, 12 Jul 2022 11:21:12 +1000 [thread overview]
Message-ID: <1657587920.49l4tue93d.astroid@bobo.none> (raw)
In-Reply-To: <20220627135347.32624-1-ldufour@linux.ibm.com>
Excerpts from Laurent Dufour's message of June 27, 2022 11:53 pm:
> When a partition is transferred, once it arrives at the destination node,
> the partition is active but much of its memory must be transferred from the
> start node.
>
> It depends on the activity in the partition, but the more CPU the partition
> has, the more memory to be transferred is likely to be. This causes latency
> when accessing pages that need to be transferred, and often, for large
> partitions, it triggers the NMI watchdog.
Importantly, it can require page in of code that runs with irqs
disabled, which is unlike a guest normally runs under PowerVM
(but it can under KVM) which is why we enabled the watchdog under
PowerVM but not KVM. So, okay it makes sense to mak an exception
for this case.
Thanks,
Nick
> The NMI watchdog causes the CPU stack to dump where it appears to be
> stuck. In this case, it does not bring much information since it can happen
> during any memory access of the kernel.
>
> In addition, the NMI interrupt mechanism is not secure and can generate a
> dump system in the event that the interruption is taken while MSR[RI]=0.
>
> Depending on the LPAR size and load, it may be interesting to extend the
> NMI watchdog timer during the LPM.
>
> That's configurable through sysctl with the new introduced variable
> (specific to powerpc) nmi_watchdog_factor. This value represents the
> percentage added to watchdog_tresh to set the NMI watchdog timeout during a
> LPM.
>
> Changes in v3:
> - don't export watchdog_mutex
> - fix a comment in mobilty.c, wait_for_vasi_session_completed()
> - fix a build issue when !CONFIG_PPC_WATCHDOG
> - rework some printk and rename the sysctl variable.
>
> v2:
> https://lore.kernel.org/all/20220614135414.37746-1-ldufour@linux.ibm.com/
>
> Laurent Dufour (4):
> powerpc/mobility: wait for memory transfer to complete
> watchdog: export lockup_detector_reconfigure
> powerpc/watchdog: introduce a NMI watchdog's factor
> pseries/mobility: set NMI watchdog factor during LPM
>
> Documentation/admin-guide/sysctl/kernel.rst | 12 +++
> arch/powerpc/include/asm/nmi.h | 2 +
> arch/powerpc/kernel/watchdog.c | 21 ++++-
> arch/powerpc/platforms/pseries/mobility.c | 85 ++++++++++++++++++++-
> include/linux/nmi.h | 2 +
> kernel/watchdog.c | 21 +++--
> 6 files changed, 135 insertions(+), 8 deletions(-)
>
> --
> 2.36.1
>
>
next prev parent reply other threads:[~2022-07-12 1:21 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 during LPM 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
2022-07-12 9:47 ` Laurent Dufour
2022-07-13 14:22 ` Laurent Dufour
2022-07-12 1:21 ` Nicholas Piggin [this message]
2022-07-12 9:32 ` [PATCH v3 0/4] Extending NMI watchdog " 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=1657587920.49l4tue93d.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;
as well as URLs for NNTP newsgroup(s).