From: Stephen Warren <swarren@wwwdotorg.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: Stephen Warren <swarren@nvidia.com>,
kexec@lists.infradead.org, Will Deacon <will.deacon@arm.com>,
linux-kernel@vger.kernel.org, Simon Horman <horms@verge.net.au>,
ebiederm@xmission.com, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: kexec: validate CPU hotplug support
Date: Tue, 30 Jul 2013 15:40:25 -0600 [thread overview]
Message-ID: <51F832C9.9000900@wwwdotorg.org> (raw)
In-Reply-To: <51E958CC.5070906@wwwdotorg.org>
On 07/19/2013 09:18 AM, Stephen Warren wrote:
> On 07/11/2013 04:48 PM, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Architectures should fully validate whether kexec is possible as part of
>> machine_kexec_prepare(), so that user-space's kexec_load() operation can
>> report any problems. Performing validation in machine_kexec() itself is
>> too late, since it is not allowed to return.
>>
>> Prior to this patch, ARM's machine_kexec() was testing after-the-fact
>> whether machine_kexec_prepare() was able to disable all but one CPU.
>> Instead, modify machine_kexec_prepare() to validate all conditions
>> necessary for machine_kexec_prepare()'s to succeed. BUG if the validation
>> succeeded, yet disabling the CPUs didn't actually work.
>
> Russell, does this look good to put into the ARM patch tracker?
I put this in the patch tracker since I assume that no response means no
objection.
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: kexec: validate CPU hotplug support
Date: Tue, 30 Jul 2013 15:40:25 -0600 [thread overview]
Message-ID: <51F832C9.9000900@wwwdotorg.org> (raw)
In-Reply-To: <51E958CC.5070906@wwwdotorg.org>
On 07/19/2013 09:18 AM, Stephen Warren wrote:
> On 07/11/2013 04:48 PM, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Architectures should fully validate whether kexec is possible as part of
>> machine_kexec_prepare(), so that user-space's kexec_load() operation can
>> report any problems. Performing validation in machine_kexec() itself is
>> too late, since it is not allowed to return.
>>
>> Prior to this patch, ARM's machine_kexec() was testing after-the-fact
>> whether machine_kexec_prepare() was able to disable all but one CPU.
>> Instead, modify machine_kexec_prepare() to validate all conditions
>> necessary for machine_kexec_prepare()'s to succeed. BUG if the validation
>> succeeded, yet disabling the CPUs didn't actually work.
>
> Russell, does this look good to put into the ARM patch tracker?
I put this in the patch tracker since I assume that no response means no
objection.
WARNING: multiple messages have this Message-ID (diff)
From: Stephen Warren <swarren@wwwdotorg.org>
To: Russell King <linux@arm.linux.org.uk>
Cc: ebiederm@xmission.com, Simon Horman <horms@verge.net.au>,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Will Deacon <will.deacon@arm.com>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] ARM: kexec: validate CPU hotplug support
Date: Tue, 30 Jul 2013 15:40:25 -0600 [thread overview]
Message-ID: <51F832C9.9000900@wwwdotorg.org> (raw)
In-Reply-To: <51E958CC.5070906@wwwdotorg.org>
On 07/19/2013 09:18 AM, Stephen Warren wrote:
> On 07/11/2013 04:48 PM, Stephen Warren wrote:
>> From: Stephen Warren <swarren@nvidia.com>
>>
>> Architectures should fully validate whether kexec is possible as part of
>> machine_kexec_prepare(), so that user-space's kexec_load() operation can
>> report any problems. Performing validation in machine_kexec() itself is
>> too late, since it is not allowed to return.
>>
>> Prior to this patch, ARM's machine_kexec() was testing after-the-fact
>> whether machine_kexec_prepare() was able to disable all but one CPU.
>> Instead, modify machine_kexec_prepare() to validate all conditions
>> necessary for machine_kexec_prepare()'s to succeed. BUG if the validation
>> succeeded, yet disabling the CPUs didn't actually work.
>
> Russell, does this look good to put into the ARM patch tracker?
I put this in the patch tracker since I assume that no response means no
objection.
next prev parent reply other threads:[~2013-07-30 21:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-11 22:48 [PATCH] ARM: kexec: validate CPU hotplug support Stephen Warren
2013-07-11 22:48 ` Stephen Warren
2013-07-11 22:48 ` Stephen Warren
2013-07-19 15:18 ` Stephen Warren
2013-07-19 15:18 ` Stephen Warren
2013-07-19 15:18 ` Stephen Warren
2013-07-30 21:40 ` Stephen Warren [this message]
2013-07-30 21:40 ` Stephen Warren
2013-07-30 21:40 ` Stephen Warren
2013-07-21 1:40 ` Eric W. Biederman
2013-07-21 1:40 ` Eric W. Biederman
2013-07-21 1:40 ` Eric W. Biederman
2013-08-01 13:41 ` Russell King - ARM Linux
2013-08-01 13:41 ` Russell King - ARM Linux
2013-08-01 13:41 ` Russell King - ARM Linux
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=51F832C9.9000900@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=ebiederm@xmission.com \
--cc=horms@verge.net.au \
--cc=kexec@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=swarren@nvidia.com \
--cc=will.deacon@arm.com \
/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.