Re: [PATCH] kgdb: Fix broken handling of printk() in NMI context

2020-05-14 Thread Sumit Garg
Hi Petr, On Thu, 14 May 2020 at 14:13, Petr Mladek wrote: > > On Wed 2020-05-13 19:04:48, Sumit Garg wrote: > > On Tue, 12 May 2020 at 19:55, Daniel Thompson > > wrote: > > > > > > On Tue, May 12, 2020 at 02:18:34PM +0530, Sumit Garg wrote: > > > > Since commit 42a0bb3f7138 ("printk/nmi:

Re: [PATCH] kgdb: Fix broken handling of printk() in NMI context

2020-05-14 Thread Petr Mladek
On Wed 2020-05-13 19:04:48, Sumit Garg wrote: > On Tue, 12 May 2020 at 19:55, Daniel Thompson > wrote: > > > > On Tue, May 12, 2020 at 02:18:34PM +0530, Sumit Garg wrote: > > > Since commit 42a0bb3f7138 ("printk/nmi: generic solution for safe printk > > > in NMI"), kgdb entry in NMI context

Re: [PATCH] kgdb: Fix broken handling of printk() in NMI context

2020-05-13 Thread Sumit Garg
On Tue, 12 May 2020 at 19:55, Daniel Thompson wrote: > > On Tue, May 12, 2020 at 02:18:34PM +0530, Sumit Garg wrote: > > Since commit 42a0bb3f7138 ("printk/nmi: generic solution for safe printk > > in NMI"), kgdb entry in NMI context defaults to use safe NMI printk() > > I didn't see the author

Re: [PATCH] kgdb: Fix broken handling of printk() in NMI context

2020-05-12 Thread Daniel Thompson
On Tue, May 12, 2020 at 02:18:34PM +0530, Sumit Garg wrote: > Since commit 42a0bb3f7138 ("printk/nmi: generic solution for safe printk > in NMI"), kgdb entry in NMI context defaults to use safe NMI printk() I didn't see the author on Cc: nor any of the folks whose hands it passed through. It

[PATCH] kgdb: Fix broken handling of printk() in NMI context

2020-05-12 Thread Sumit Garg
Since commit 42a0bb3f7138 ("printk/nmi: generic solution for safe printk in NMI"), kgdb entry in NMI context defaults to use safe NMI printk() which involves CPU specific buffers and deferred printk() until exit from NMI context. But kgdb being a stop-the-world debugger, we don't want to defer