Re: [PATCH tip/locking/core] kcsan: Improve IRQ state trace reporting

On Tue, 28 Jul 2020 at 13:30, Ingo Molnar wrote: > > > * Marco Elver wrote: > > > To improve the general usefulness of the IRQ state trace information > > with KCSAN enabled, save and restore the trace information when entering > > and exiting the KCSAN runtime as well as when generating a KCSAN

Re: [PATCH tip/locking/core] kcsan: Improve IRQ state trace reporting

* Marco Elver wrote: > To improve the general usefulness of the IRQ state trace information > with KCSAN enabled, save and restore the trace information when entering > and exiting the KCSAN runtime as well as when generating a KCSAN report. > > Without this, reporting the IRQ state trace (whe

Re: [PATCH tip/locking/core] kcsan: Improve IRQ state trace reporting

On Mon, 20 Jul 2020 at 14:03, Marco Elver wrote: > > To improve the general usefulness of the IRQ state trace information > with KCSAN enabled, save and restore the trace information when entering > and exiting the KCSAN runtime as well as when generating a KCSAN report. > > Without this, reportin

[PATCH tip/locking/core] kcsan: Improve IRQ state trace reporting

To improve the general usefulness of the IRQ state trace information with KCSAN enabled, save and restore the trace information when entering and exiting the KCSAN runtime as well as when generating a KCSAN report. Without this, reporting the IRQ state trace (whether via a KCSAN report or outside