Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-02 Thread Ingo Molnar
* Ingo Molnar wrote: > > * Peter Zijlstra wrote: > > > On Mon, Mar 01, 2021 at 08:16:12PM +0100, Jürgen Groß wrote: > > > >https://lkml.kernel.org/r/20210220231712.2475218-2-na...@vmware.com > > > > > > They are already in tip locking/core (Ingo applied them). > > > > I'm very tempted

Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-02 Thread Ingo Molnar
* Peter Zijlstra wrote: > On Mon, Mar 01, 2021 at 08:16:12PM +0100, Jürgen Groß wrote: > > >https://lkml.kernel.org/r/20210220231712.2475218-2-na...@vmware.com > > > > They are already in tip locking/core (Ingo applied them). > > I'm very tempted to undo that :-( Sorry about that - I'm s

Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-02 Thread Jürgen Groß
On 01.03.21 18:07, Peter Zijlstra wrote: On Mon, Mar 01, 2021 at 11:13:36AM +0100, Juergen Gross wrote: In order to help identifying problems with IPI handling and remote function execution add some more data to IPI debugging code. There have been multiple reports of cpus looping long times (ma

Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-01 Thread Peter Zijlstra
On Mon, Mar 01, 2021 at 08:16:12PM +0100, Jürgen Groß wrote: > >https://lkml.kernel.org/r/20210220231712.2475218-2-na...@vmware.com > > They are already in tip locking/core (Ingo applied them). I'm very tempted to undo that :-(

Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-01 Thread Jürgen Groß
On 01.03.21 18:07, Peter Zijlstra wrote: On Mon, Mar 01, 2021 at 11:13:36AM +0100, Juergen Gross wrote: In order to help identifying problems with IPI handling and remote function execution add some more data to IPI debugging code. There have been multiple reports of cpus looping long times (ma

Re: [PATCH v2 3/3] kernel/smp: add more data to CSD lock debugging

2021-03-01 Thread Peter Zijlstra
On Mon, Mar 01, 2021 at 11:13:36AM +0100, Juergen Gross wrote: > In order to help identifying problems with IPI handling and remote > function execution add some more data to IPI debugging code. > > There have been multiple reports of cpus looping long times (many > seconds) in smp_call_function_m