All of lore.kernel.org
 help / color / mirror / Atom feed
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: decouple CPU offlining from reboot/shutdown
Date: Wed, 12 Jun 2013 12:15:11 -0600	[thread overview]
Message-ID: <51B8BAAF.8060405@wwwdotorg.org> (raw)
In-Reply-To: <20130612180912.GW18614@n2100.arm.linux.org.uk>

On 06/12/2013 12:09 PM, Russell King - ARM Linux wrote:
> On Tue, Jun 11, 2013 at 07:29:27PM +0100, Will Deacon wrote:
>> Yes. Usually this is a path of no return, but if we detect an error before
>> we've changed stack then I think we should at least try to propogate the
>> error.
> 
> Except, if you make soft_restart able to return an error, then you really
> need machine_restart() to do the same, but that's a cross-arch function.

I was tempted to just printk and make them return. It looks like kexec
will just return back out of its call path without issue.

I suppose adjusting the function signature of machine_kexec() to
propagate an error code back would be useful, and probably wouldn't be
too much churn.

> And what do you do when you hit a soft-watchdog event and it calls
> machine_restart(), which then decides to fail?  Or a panic event and
> machine_restart() fails?

Well, if you're using soft_restart with SMP, those case already don't
work, right?

  reply	other threads:[~2013-06-12 18:15 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-10 18:12 [PATCH] ARM: decouple CPU offlining from reboot/shutdown Stephen Warren
2013-06-11 17:23 ` Will Deacon
2013-06-11 18:08   ` Stephen Warren
2013-06-11 18:29     ` Will Deacon
2013-06-11 18:38       ` Stephen Warren
2013-06-12 16:58         ` Will Deacon
2013-06-12 18:09       ` Russell King - ARM Linux
2013-06-12 18:15         ` Stephen Warren [this message]
2013-06-11 18:41   ` Stephen Warren
2013-06-12 17:01     ` Will Deacon
2013-06-12 18:40       ` Stephen Warren

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=51B8BAAF.8060405@wwwdotorg.org \
    --to=swarren@wwwdotorg.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.