[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180214133239.498a1e73@balbir.ozlabs.ibm.com>
Date: Wed, 14 Feb 2018 13:32:39 +1100
From: Balbir Singh <bsingharora@...il.com>
To: Guenter Roeck <linux@...ck-us.net>
Cc: Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Paul Mackerras <paulus@...ba.org>,
Michael Ellerman <mpe@...erman.id.au>,
"open list:LINUX FOR POWERPC (32-BIT AND 64-BIT)"
<linuxppc-dev@...ts.ozlabs.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Nicholas Piggin <npiggin@...il.com>
Subject: Re: [PATCH 1/2] powerpc/kdump: Add missing optional dummy functions
On Mon, 12 Feb 2018 15:25:51 -0800
Guenter Roeck <linux@...ck-us.net> wrote:
> On Tue, Feb 13, 2018 at 10:01:57AM +1100, Balbir Singh wrote:
> > On Tue, Feb 13, 2018 at 9:34 AM, Guenter Roeck <linux@...ck-us.net> wrote:
> > > If KEXEC_CORE is not enabled, PowerNV builds fail as follows.
> > >
> > > arch/powerpc/platforms/powernv/smp.c: In function 'pnv_smp_cpu_kill_self':
> > > arch/powerpc/platforms/powernv/smp.c:236:4: error:
> > > implicit declaration of function 'crash_ipi_callback'
> > >
> > > Add dummy function calls, similar to kdump_in_progress(), to solve the
> > > problem.
> > >
> > > Fixes: 4145f358644b ("powernv/kdump: Fix cases where the kdump kernel ...")
> > > Cc: Balbir Singh <bsingharora@...il.com>
> > > Cc: Michael Ellerman <mpe@...erman.id.au>
> > > Cc: Nicholas Piggin <npiggin@...il.com>
> > > Signed-off-by: Guenter Roeck <linux@...ck-us.net>
> > > ---
> >
> > Thanks for working on this.
> >
> > You've added two functions, I understand the crash_send_ipi() bits
> > that I broke. Looks like crash_ipi_callback broken without KEXEC_CORE?
> >
>
> If I recall correctly, 4145f358644b introduced the call to crash_ipi_callback().
> After I declared the dummy function for that, I got an error about the missing
> crash_send_ipi(). I didn't spend more time on it but just added another dummy
> function. It may well be that another problem was introduced in the same time
> frame. On the other side, maybe I got it all wrong, and my patch is not worth
> the computer it was written on.
>
The patches worked for me with CONFIG_KEXEC=n and CONFIG_KEXEC_CORE=n
Tested-by: Balbir Singh <bsingharora@...il.com>
Balbir Singh
Powered by blists - more mailing lists