Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.kernel > #1640509
| From | Dinh Nguyen <dinguyen@kernel.org> |
|---|---|
| Newsgroups | linux.kernel |
| Subject | Re: [PATCH] socfpga_a10: reset CPU1 in socfpga_cpu_kill() |
| Date | 2017-05-12 16:30 +0200 |
| Message-ID | <tGjJU-5NS-9@gated-at.bofh.it> (permalink) |
| References | <tFscx-4VM-1@gated-at.bofh.it> <tFscx-4VM-5@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 05/10/2017 12:13 AM, yanjiang.jin@windriver.com wrote:
> From: Yanjiang Jin <yanjiang.jin@windriver.com>
>
> Kexec's second kernel would hang if CPU1 isn't reset.
>
Can you please be a bit more descriptive on the commit log? Is it
because when kexec starts, the SMP on the kexec's kernel try to run on CPU1?
> Signed-off-by: Yanjiang Jin <yanjiang.jin@windriver.com>
> ---
> arch/arm/mach-socfpga/platsmp.c | 12 +++++++++++-
> 1 file changed, 11 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm/mach-socfpga/platsmp.c b/arch/arm/mach-socfpga/platsmp.c
> index 0ee7677..db3940e 100644
> --- a/arch/arm/mach-socfpga/platsmp.c
> +++ b/arch/arm/mach-socfpga/platsmp.c
> @@ -117,6 +117,16 @@ static int socfpga_cpu_kill(unsigned int cpu)
> {
> return 1;
> }
> +
> +static int socfpga_a10_cpu_kill(unsigned int cpu)
> +{
> + /* This will put CPU #1 into reset. */
> + if (socfpga_cpu1start_addr)
Do you need to check for socfpga_cpu1start_addr?
Dinh
Back to linux.kernel | Previous | Next | Find similar | Unroll thread
Re: [PATCH] socfpga_a10: reset CPU1 in socfpga_cpu_kill() Dinh Nguyen <dinguyen@kernel.org> - 2017-05-12 16:30 +0200
csiph-web