From: Song Liu <songliubraving@meta.com>
To: Song Liu <songliubraving@meta.com>
Cc: Song Liu <song@kernel.org>, LKML <linux-kernel@vger.kernel.org>,
Kernel Team <kernel-team@meta.com>,
Andrew Morton <akpm@linux-foundation.org>,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v4] watchdog: Allow nmi watchdog to use "ref-cycles" event
Date: Fri, 2 Jun 2023 22:11:51 +0000 [thread overview]
Message-ID: <393545F8-AB12-47F6-9293-75B2274CF7B2@fb.com> (raw)
In-Reply-To: <5F882BF2-6B6A-4809-B0D5-9EF430E11C2F@fb.com>
Hi Andrew and Peter,
Friendly ping... Any comment on this one?
Thanks,
Song
> On May 25, 2023, at 3:20 PM, Song Liu <songliubraving@meta.com> wrote:
>
> Hi Andrew and Peter,
>
>
>> On May 19, 2023, at 9:59 AM, Song Liu <songliubraving@meta.com> wrote:
>>
>> Hi Andrew and Peter,
>>
>> Does this version look good do you?
>>
>> Thanks,
>> Song
>>
>>> On May 17, 2023, at 5:25 PM, Song Liu <song@kernel.org> wrote:
>>>
>>> NMI watchdog permanently consumes one hardware counters per CPU on the
>>> system. For systems that use many hardware counters, this causes more
>>> aggressive time multiplexing of perf events.
>>>
>>> OTOH, some CPUs (mostly Intel) support "ref-cycles" event, which is rarely
>>> used. Add kernel cmdline arg nmi_watchdog=ref-cycles to configure the
>>> watchdog to use "ref-cycles" event instead of "cycles".
>>>
>>> Cc: Andrew Morton <akpm@linux-foundation.org>
>>> Cc: Peter Zijlstra <peterz@infradead.org>
>>> Signed-off-by: Song Liu <song@kernel.org>
>
> Could you please share your comments on this patch?
>
> Thanks,
> Song
next prev parent reply other threads:[~2023-06-02 22:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-18 0:25 Song Liu
2023-05-18 6:44 ` Yonghong Song
2023-05-18 20:12 ` Song Liu
2023-05-19 16:59 ` Song Liu
2023-05-25 22:20 ` Song Liu
2023-06-02 22:11 ` Song Liu [this message]
2023-06-02 22:47 ` Peter Zijlstra
2023-06-02 23:15 ` Song Liu
2023-06-08 18:18 ` Song Liu
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=393545F8-AB12-47F6-9293-75B2274CF7B2@fb.com \
--to=songliubraving@meta.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=song@kernel.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®