Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-03 Thread David Gibson
On Mon, Dec 04, 2017 at 04:12:06PM +1000, Nicholas Piggin wrote: > On Mon, 4 Dec 2017 16:49:14 +1100 > David Gibson wrote: > > > On Fri, Dec 01, 2017 at 09:40:38PM +1000, Nicholas Piggin wrote: > > > On Fri, 01 Dec 2017 22:11:50 +1100 > > > Michael Ellerman wrote: > > > > > > > David Gibson

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-03 Thread Nicholas Piggin
On Mon, 4 Dec 2017 16:49:14 +1100 David Gibson wrote: > On Fri, Dec 01, 2017 at 09:40:38PM +1000, Nicholas Piggin wrote: > > On Fri, 01 Dec 2017 22:11:50 +1100 > > Michael Ellerman wrote: > > > > > David Gibson writes: > > > > > > > On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggi

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-03 Thread David Gibson
On Fri, Dec 01, 2017 at 10:11:50PM +1100, Michael Ellerman wrote: > David Gibson writes: > > > On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: > >> On Wed, 29 Nov 2017 15:06:52 +1100 > >> David Gibson wrote: > >> > >> > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump pani

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-03 Thread David Gibson
On Fri, Dec 01, 2017 at 09:40:38PM +1000, Nicholas Piggin wrote: > On Fri, 01 Dec 2017 22:11:50 +1100 > Michael Ellerman wrote: > > > David Gibson writes: > > > > > On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: > > >> On Wed, 29 Nov 2017 15:06:52 +1100 > > >> David Gibson

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-03 Thread David Gibson
On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: > On Wed, 29 Nov 2017 15:06:52 +1100 > David Gibson wrote: > > > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic notifier" > > purports to fix a problem when the kernel panics with fadump not > > registered, but it break

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-01 Thread Nicholas Piggin
On Fri, 01 Dec 2017 22:11:50 +1100 Michael Ellerman wrote: > David Gibson writes: > > > On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: > >> On Wed, 29 Nov 2017 15:06:52 +1100 > >> David Gibson wrote: > >> > >> > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic

Re: a3b2cb30 broken panic reporting for qemu guests

2017-12-01 Thread Michael Ellerman
David Gibson writes: > On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: >> On Wed, 29 Nov 2017 15:06:52 +1100 >> David Gibson wrote: >> >> > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic notifier" >> > purports to fix a problem when the kernel panics with fadump no

Re: a3b2cb30 broken panic reporting for qemu guests

2017-11-30 Thread David Gibson
On Wed, Nov 29, 2017 at 02:23:43PM +1000, Nicholas Piggin wrote: > On Wed, 29 Nov 2017 15:06:52 +1100 > David Gibson wrote: > > > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic notifier" > > purports to fix a problem when the kernel panics with fadump not > > registered, but it break

Re: a3b2cb30 broken panic reporting for qemu guests

2017-11-28 Thread Nicholas Piggin
On Wed, 29 Nov 2017 15:06:52 +1100 David Gibson wrote: > a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic notifier" > purports to fix a problem when the kernel panics with fadump not > registered, but it breaks something else instead. I _think_ it was > working on the incorrect assump

a3b2cb30 broken panic reporting for qemu guests

2017-11-28 Thread David Gibson
a3b2cb30 "powerpc: Do not call ppc_md.panic in fadump panic notifier" purports to fix a problem when the kernel panics with fadump not registered, but it breaks something else instead. I _think_ it was working on the incorrect assumption that ppc_md.panic was (or should be) only used with fadump,