From: Michael Neuling <mikey@neuling.org>
To: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
Cc: linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH] powerpc/xics: Adjust interrupt receive priority for offline cpus
Date: Fri, 24 Feb 2017 11:22:02 +1100 [thread overview]
Message-ID: <1487895722.16514.8.camel@neuling.org> (raw)
In-Reply-To: <20170223105443.22029-1-svaidy@linux.vnet.ibm.com>
On Thu, 2017-02-23 at 16:24 +0530, Vaidyanathan Srinivasan wrote:
> Offline CPUs need to receive IPIs through XIVE when they are
> in stop state and wakeup from that state.
>=20
> Reduce interrupt receive priority in order to receive XIVE
> wakeup interrupts when in offline state.
>=20
> LOWEST_PRIORITY would allow all interrupts to be delivered
> as wakeup events.
This needs to be expanded to explain why "DEFAULT" doesn't work in this cas=
e.
This also needs an explicit statement that "It fixes onlining of CPUs on
POWER9". I'd even advocate for making that the patch subject.=20
Also if it's the right fix, it needs a cc:stable.
Mikey
> Signed-off-by: Vaidyanathan Srinivasan <svaidy@linux.vnet.ibm.com>
> ---
> =C2=A0arch/powerpc/sysdev/xics/xics-common.c | 2 +-
> =C2=A01 file changed, 1 insertion(+), 1 deletion(-)
>=20
> diff --git a/arch/powerpc/sysdev/xics/xics-common.c
> b/arch/powerpc/sysdev/xics/xics-common.c
> index 69d858e..c674a9d 100644
> --- a/arch/powerpc/sysdev/xics/xics-common.c
> +++ b/arch/powerpc/sysdev/xics/xics-common.c
> @@ -199,7 +199,7 @@ void xics_migrate_irqs_away(void)
> =C2=A0 xics_set_cpu_giq(xics_default_distrib_server, 0);
> =C2=A0
> =C2=A0 /* Allow IPIs again... */
> - icp_ops->set_priority(DEFAULT_PRIORITY);
> + icp_ops->set_priority(LOWEST_PRIORITY);
> =C2=A0
> =C2=A0 for_each_irq_desc(virq, desc) {
> =C2=A0 struct irq_chip *chip;
next prev parent reply other threads:[~2017-02-24 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:54 [PATCH] powerpc/xics: Adjust interrupt receive priority for offline cpus Vaidyanathan Srinivasan
2017-02-24 0:22 ` Michael Neuling [this message]
2017-02-24 0:35 ` Balbir Singh
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=1487895722.16514.8.camel@neuling.org \
--to=mikey@neuling.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=svaidy@linux.vnet.ibm.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 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).