From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ego@linux.vnet.ibm.com,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
matt@ozlabs.org, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, suzuki@in.ibm.com,
ebiederm@xmission.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] powerpc, kexec: Fix "Processor X is stuck" issue during kexec from ST mode
Date: Fri, 06 Jun 2014 18:07:18 +0530 [thread overview]
Message-ID: <5391B5FE.2090508@linux.vnet.ibm.com> (raw)
In-Reply-To: <5391B413.100@linux.vnet.ibm.com>
On 06/06/2014 05:59 PM, Srivatsa S. Bhat wrote:
> +bool kexec_cpu_wake(void)
> +{
> + kexec_smp_down(NULL);
> +
> + /* NOTREACHED */
> + return true;
> +}
> +
This function doesn't have to return anything, so we can define it as void.
The bool is a remnant of my previous attempt at making this work. (But these
patches compile fine as they are, though).
Regards,
Srivatsa S. Bhat
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ego@linux.vnet.ibm.com, matt@ozlabs.org,
mahesh@linux.vnet.ibm.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, suzuki@in.ibm.com,
ebiederm@xmission.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, Vivek Goyal <vgoyal@redhat.com>
Subject: Re: [PATCH] powerpc, kexec: Fix "Processor X is stuck" issue during kexec from ST mode
Date: Fri, 06 Jun 2014 18:07:18 +0530 [thread overview]
Message-ID: <5391B5FE.2090508@linux.vnet.ibm.com> (raw)
In-Reply-To: <5391B413.100@linux.vnet.ibm.com>
On 06/06/2014 05:59 PM, Srivatsa S. Bhat wrote:
> +bool kexec_cpu_wake(void)
> +{
> + kexec_smp_down(NULL);
> +
> + /* NOTREACHED */
> + return true;
> +}
> +
This function doesn't have to return anything, so we can define it as void.
The bool is a remnant of my previous attempt at making this work. (But these
patches compile fine as they are, though).
Regards,
Srivatsa S. Bhat
WARNING: multiple messages have this Message-ID (diff)
From: "Srivatsa S. Bhat" <srivatsa.bhat@linux.vnet.ibm.com>
To: Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: ego@linux.vnet.ibm.com, matt@ozlabs.org,
mahesh@linux.vnet.ibm.com, kexec@lists.infradead.org,
linux-kernel@vger.kernel.org, suzuki@in.ibm.com,
ebiederm@xmission.com, paulus@samba.org,
linuxppc-dev@lists.ozlabs.org, Vivek Goyal <vgoyal@redhat.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH] powerpc, kexec: Fix "Processor X is stuck" issue during kexec from ST mode
Date: Fri, 06 Jun 2014 18:07:18 +0530 [thread overview]
Message-ID: <5391B5FE.2090508@linux.vnet.ibm.com> (raw)
In-Reply-To: <5391B413.100@linux.vnet.ibm.com>
On 06/06/2014 05:59 PM, Srivatsa S. Bhat wrote:
> +bool kexec_cpu_wake(void)
> +{
> + kexec_smp_down(NULL);
> +
> + /* NOTREACHED */
> + return true;
> +}
> +
This function doesn't have to return anything, so we can define it as void.
The bool is a remnant of my previous attempt at making this work. (But these
patches compile fine as they are, though).
Regards,
Srivatsa S. Bhat
next prev parent reply other threads:[~2014-06-06 12:39 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-27 10:55 [PATCH] powerpc, kexec: Fix "Processor X is stuck" issue during kexec from ST mode Srivatsa S. Bhat
2014-05-27 10:55 ` Srivatsa S. Bhat
2014-05-27 10:55 ` Srivatsa S. Bhat
2014-05-28 13:31 ` Vivek Goyal
2014-05-28 13:31 ` Vivek Goyal
2014-05-28 13:31 ` Vivek Goyal
2014-06-03 20:28 ` Srivatsa S. Bhat
2014-06-03 20:28 ` Srivatsa S. Bhat
2014-06-03 20:28 ` Srivatsa S. Bhat
2014-06-03 22:09 ` Benjamin Herrenschmidt
2014-06-03 22:09 ` Benjamin Herrenschmidt
2014-06-03 22:09 ` Benjamin Herrenschmidt
2014-06-04 13:46 ` Vivek Goyal
2014-06-04 13:46 ` Vivek Goyal
2014-06-04 13:46 ` Vivek Goyal
2014-06-06 12:30 ` Srivatsa S. Bhat
2014-06-06 12:30 ` Srivatsa S. Bhat
2014-06-06 12:30 ` Srivatsa S. Bhat
2014-06-06 18:27 ` Vivek Goyal
2014-06-06 18:27 ` Vivek Goyal
2014-06-06 18:27 ` Vivek Goyal
2014-06-06 19:00 ` Srivatsa S. Bhat
2014-06-06 19:00 ` Srivatsa S. Bhat
2014-06-06 19:00 ` Srivatsa S. Bhat
2014-06-06 12:29 ` Srivatsa S. Bhat
2014-06-06 12:29 ` Srivatsa S. Bhat
2014-06-06 12:29 ` Srivatsa S. Bhat
2014-06-06 12:37 ` Srivatsa S. Bhat [this message]
2014-06-06 12:37 ` Srivatsa S. Bhat
2014-06-06 12:37 ` Srivatsa S. Bhat
2014-06-06 21:16 ` Srivatsa S. Bhat
2014-06-06 21:16 ` Srivatsa S. Bhat
2014-06-06 21:16 ` Srivatsa S. Bhat
2014-06-12 6:39 ` Joel Stanley
2014-06-12 6:39 ` Joel Stanley
2014-06-12 6:39 ` Joel Stanley
2014-06-12 8:17 ` Srivatsa S. Bhat
2014-06-12 8:17 ` Srivatsa S. Bhat
2014-06-12 8:17 ` Srivatsa S. Bhat
2014-06-04 13:41 ` Vivek Goyal
2014-06-04 13:41 ` Vivek Goyal
2014-06-04 13:41 ` Vivek Goyal
2014-06-06 12:31 ` Srivatsa S. Bhat
2014-06-06 12:31 ` Srivatsa S. Bhat
2014-06-06 12:31 ` Srivatsa S. Bhat
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=5391B5FE.2090508@linux.vnet.ibm.com \
--to=srivatsa.bhat@linux.vnet.ibm.com \
--cc=ananth@in.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=ebiederm@xmission.com \
--cc=ego@linux.vnet.ibm.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=matt@ozlabs.org \
--cc=paulus@samba.org \
--cc=suzuki@in.ibm.com \
--cc=vgoyal@redhat.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.