From: Michael Ellerman <patch-notifications@ellerman•id.au>
To: Nicholas Piggin <npiggin@gmail•com>
Cc: linuxppc-dev@lists•ozlabs.org, Nicholas Piggin <npiggin@gmail•com>
Subject: Re: [1/4] powerpc: change the doorbell IPI calling convention
Date: Wed, 19 Apr 2017 13:47:17 +1000 (AEST) [thread overview]
Message-ID: <3w77H91kH3z9s7L@ozlabs.org> (raw)
In-Reply-To: <20170413101624.26628-2-npiggin@gmail.com>
On Thu, 2017-04-13 at 10:16:21 UTC, Nicholas Piggin wrote:
> Change the doorbell callers to know about their msgsnd addressing,
> rather than have them set a per-cpu target data tag at boot that gets
> sent to the cause_ipi functions. The data is only used for doorbell IPI
> functions, no other IPI types, so it makes sense to keep that detail
> local to doorbell.
>
> Have the platform code understand doorbell IPIs, rather than the
> interrupt controller code understand them. Platform code can look at
> capabilities it has available and decide which to use.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail•com>
Series applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/b866cc2199d6a6cdcefe4acfe4cfca
cheers
next prev parent reply other threads:[~2017-04-19 3:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-13 10:16 [PATCH 0/4 v2] doorbell patches for POWER9 Nicholas Piggin
2017-04-13 10:16 ` [PATCH 1/4] powerpc: change the doorbell IPI calling convention Nicholas Piggin
2017-04-19 3:47 ` Michael Ellerman [this message]
2017-04-13 10:16 ` [PATCH 2/4] powerpc: Introduce msgsnd/doorbell barrier primitives Nicholas Piggin
2017-04-13 10:16 ` [PATCH 3/4] powerpc/64s: avoid branch for ppc_msgsnd Nicholas Piggin
2017-04-13 10:16 ` [PATCH 4/4] powerpc/powernv: POWER9 support for msgsnd/doorbell IPI Nicholas Piggin
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=3w77H91kH3z9s7L@ozlabs.org \
--to=patch-notifications@ellerman$(echo .)id.au \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
--cc=npiggin@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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