Re: [PATCH v3 0/5] Rework system pressure interface to the scheduler

On Wed, 10 Jan 2024 at 19:10, Dietmar Eggemann wrote: > > On 09/01/2024 14:29, Vincent Guittot wrote: > > On Tue, 9 Jan 2024 at 12:34, Dietmar Eggemann > > wrote: > >> > >> On 08/01/2024 14:48, Vincent Guittot wrote: > >>> Following the consolidation and cleanup of CPU capacity in [1], this seri

Re: [PATCH v3] tracing: Support to dump instance traces by ftrace_dump_on_oops

On Fri, 19 Jan 2024 16:08:24 +0800 Huang Yiwei wrote: > - ftrace_dump_on_oops[=orig_cpu] > + ftrace_dump_on_oops[=orig_cpu | =] I wonder if we should have it be: ftrace_dump_on_oops[=orig_cpu | = | =:orig_cpu ] Then last would be to only print out a specific CPU trace of the gi

[PATCH v3] tracing: Support to dump instance traces by ftrace_dump_on_oops

Currently ftrace only dumps the global trace buffer on an OOPs. For debugging a production usecase, instance trace will be helpful to check specific problems since global trace buffer may be used for other purposes. This patch extend the ftrace_dump_on_oops parameter to dump a specific trace insta