From: Michael Ellerman <mpe@ellerman.id.au>
To: Laurent Dufour <ldufour@linux.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
npiggin@gmail.com, christophe.leroy@csgroup.eu,
wim@linux-watchdog.org, linux@roeck-us.net,
nathanl@linux.ibm.com
Cc: haren@linux.vnet.ibm.com, hch@infradead.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
linux-watchdog@vger.kernel.org
Subject: Re: [PATCH v5 4/4] pseries/mobility: set NMI watchdog factor during an LPM
Date: Tue, 26 Jul 2022 20:53:21 +1000 [thread overview]
Message-ID: <878rogb0wu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <4e366d73-fb9f-bd83-abd0-c624a737a0cd@linux.ibm.com>
Laurent Dufour <ldufour@linux.ibm.com> writes:
> Le 13/07/2022 à 22:17, Randy Dunlap a écrit :
>> 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
>
> Thanks, Randy.
>
> Michael, could you fix that when applying the series?
Yes, I did.
cheers
WARNING: multiple messages have this Message-ID (diff)
From: Michael Ellerman <mpe@ellerman.id.au>
To: Laurent Dufour <ldufour@linux.ibm.com>,
Randy Dunlap <rdunlap@infradead.org>,
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 v5 4/4] pseries/mobility: set NMI watchdog factor during an LPM
Date: Tue, 26 Jul 2022 20:53:21 +1000 [thread overview]
Message-ID: <878rogb0wu.fsf@mpe.ellerman.id.au> (raw)
In-Reply-To: <4e366d73-fb9f-bd83-abd0-c624a737a0cd@linux.ibm.com>
Laurent Dufour <ldufour@linux.ibm.com> writes:
> Le 13/07/2022 à 22:17, Randy Dunlap a écrit :
>> 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
>
> Thanks, Randy.
>
> Michael, could you fix that when applying the series?
Yes, I did.
cheers
next prev parent reply other threads:[~2022-07-26 10:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-13 15:47 [PATCH v5 0/4] Extending NMI watchdog during LPM Laurent Dufour
2022-07-13 15:47 ` Laurent Dufour
2022-07-13 15:47 ` [PATCH v5 1/4] powerpc/mobility: wait for memory transfer to complete Laurent Dufour
2022-07-13 15:47 ` Laurent Dufour
2022-07-13 15:47 ` [PATCH v5 2/4] watchdog: export lockup_detector_reconfigure Laurent Dufour
2022-07-13 15:47 ` Laurent Dufour
2022-07-13 15:47 ` [PATCH v5 3/4] powerpc/watchdog: introduce a NMI watchdog's factor Laurent Dufour
2022-07-13 15:47 ` Laurent Dufour
2022-07-13 15:47 ` [PATCH v5 4/4] pseries/mobility: set NMI watchdog factor during an LPM Laurent Dufour
2022-07-13 15:47 ` Laurent Dufour
2022-07-13 20:17 ` Randy Dunlap
2022-07-13 20:17 ` Randy Dunlap
2022-07-25 12:25 ` Laurent Dufour
2022-07-25 12:25 ` Laurent Dufour
2022-07-26 10:53 ` Michael Ellerman [this message]
2022-07-26 10:53 ` Michael Ellerman
2022-07-29 13:02 ` [PATCH v5 0/4] Extending NMI watchdog during LPM Michael Ellerman
2022-07-29 13:02 ` Michael Ellerman
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=878rogb0wu.fsf@mpe.ellerman.id.au \
--to=mpe@ellerman.id.au \
--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=nathanl@linux.ibm.com \
--cc=npiggin@gmail.com \
--cc=rdunlap@infradead.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.