From: geoff@infradead.org (Geoff Levand)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v21 3/8] arm64: kdump: implement machine_crash_shutdown()
Date: Thu, 07 Jul 2016 09:42:34 -0700 [thread overview]
Message-ID: <1467909754.8880.56.camel@infradead.org> (raw)
In-Reply-To: <20160707004330.GU20774@linaro.org>
Hi,
On Thu, 2016-07-07 at 09:43 +0900, AKASHI Takahiro wrote:
> On Wed, Jul 06, 2016 at 10:28:57AM -0700, Geoff Levand wrote:
> > On Wed, 2016-07-06 at 16:52 +0900, AKASHI Takahiro wrote:
> > > @@ -830,6 +855,14 @@ void handle_IPI(int ipinr, struct pt_regs
> > > *regs)
> > > > > > > > > > > > > > > > > > irq_exit();
> > > > > > > > > > > > > > > > > > break;
> > >
> > > +#ifdef CONFIG_KEXEC_CORE
> > > +> > > > > > > > case IPI_CPU_CRASH_STOP:
> > > +> > > > > > > > > > > > > > > irq_enter();
> > > +> > > > > > > > > > > > > > > ipi_cpu_crash_stop(cpu, regs);
> > > +
> > > +> > > > > > > > > > > > > > > unreachable();
> > > +#endif
> >
> > It seems like you could simplifiy with something like:
> >
> > > > case IPI_CPU_CRASH_STOP:
> > > > > > if (IS_ENABLED(CONFIG_KEXEC_CORE) {
> > > > > > > > irq_enter();
> > > > > > > > ipi_cpu_crash_stop(cpu, regs);
> > > > > > > > unreachable();
> > > > > > }
>
> OK, I will take this.
>
> > Then move the CONFIG_KEXEC_CORE conditional around
> > ipi_cpu_crash_stop to just around crash_save_cpu().
>
> Yeah, we can do that, but I added these conditionals just because
> the kernel size can be reduced (a bit, obviously) if kexec is
> not needed.
The linker will remove the unused ipi_cpu_crash_stop since
it is static. atomic_t waiting_for_crash_ipi also becomes
unused, and I think it will be removed also. The motivation
for these changes is to get a build test of this code
even when CONFIG_KEXEC_CORE=n.
-Geoff
next prev parent reply other threads:[~2016-07-07 16:42 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-06 7:52 [PATCH v21 0/8] arm64: kdump support AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 1/8] arm64: kdump: reserve memory for crash dump kernel AKASHI Takahiro
2016-07-06 17:00 ` Geoff Levand
2016-07-07 0:19 ` AKASHI Takahiro
2016-07-06 18:11 ` Thiago Jung Bauermann
2016-07-07 1:17 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 2/8] arm64: limit memory regions based on DT property, usable-memory AKASHI Takahiro
2016-07-06 17:48 ` Geoff Levand
2016-07-06 7:52 ` [PATCH v21 3/8] arm64: kdump: implement machine_crash_shutdown() AKASHI Takahiro
2016-07-06 17:28 ` Geoff Levand
2016-07-07 0:43 ` AKASHI Takahiro
2016-07-07 16:42 ` Geoff Levand [this message]
2016-07-06 7:52 ` [PATCH v21 4/8] arm64: kdump: add kdump support AKASHI Takahiro
2016-07-06 17:38 ` Geoff Levand
2016-07-07 0:49 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 5/8] arm64: kdump: add VMCOREINFO's for user-space coredump tools AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 6/8] arm64: kdump: enable kdump in the arm64 defconfig AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 7/8] arm64: kdump: update a kernel doc AKASHI Takahiro
2016-07-06 17:44 ` Geoff Levand
2016-07-07 0:51 ` AKASHI Takahiro
2016-07-06 7:52 ` [PATCH v21 8/8] Documentation: dt: usable-memory and elfcorehdr nodes for arm64 kexec AKASHI Takahiro
2016-07-06 17:46 ` Geoff Levand
2016-07-06 19:29 ` Thiago Jung Bauermann
2016-07-07 2:00 ` AKASHI Takahiro
2016-07-07 18:46 ` Thiago Jung Bauermann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1467909754.8880.56.camel@infradead.org \
--to=geoff@infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).