Hello,
On Mon, Jan 22, 2024 at 08:55:39PM -0500, Steven Rostedt wrote:
> On Tue, 23 Jan 2024 09:44:43 +0800
> George Guo wrote:
>
> > There are two reasons of percpu_alloc failed without warnings:
> >
> > 1. do_warn is false
> > 2. do_warn is true and warn_limit is reached the limit.
>
> Yes
On Tue, 23 Jan 2024 09:44:43 +0800
George Guo wrote:
> There are two reasons of percpu_alloc failed without warnings:
>
> 1. do_warn is false
> 2. do_warn is true and warn_limit is reached the limit.
Yes I know the reasons.
>
> Showing do_warn and warn_limit makes things simple, maybe dont
On Mon, 22 Jan 2024 10:57:00 -0500
Steven Rostedt wrote:
> On Mon, 22 Jan 2024 15:36:29 +0800
> George Guo wrote:
>
> > From: George Guo
> >
> > Add do_warn, warn_limit fields to the output of the
> > percpu_alloc_percpu_fail ftrace event.
> >
> > This is required to percpu_alloc failed
On Mon, 22 Jan 2024 15:36:29 +0800
George Guo wrote:
> From: George Guo
>
> Add do_warn, warn_limit fields to the output of the
> percpu_alloc_percpu_fail ftrace event.
>
> This is required to percpu_alloc failed with no warning showing.
You mean to state;
In order to know why
From: George Guo
Add do_warn, warn_limit fields to the output of the
percpu_alloc_percpu_fail ftrace event.
This is required to percpu_alloc failed with no warning showing.
Signed-off-by: George Guo
---
include/trace/events/percpu.h | 22 ++
mm/percpu.c
5 matches
Mail list logo
