linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Ritesh Harjani (IBM) <riteshh@linux.ibm.com>
To: Gautam Menghani <gautam@linux.ibm.com>,
	maddy@linux.ibm.com, mpe@ellerman.id.au, npiggin@gmail.com,
	christophe.leroy@csgroup.eu
Cc: Gautam Menghani <gautam@linux.ibm.com>,
	linuxppc-dev@lists.ozlabs.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] powerpc: Remove duplicate definition for ppc_msgsnd_sync()
Date: Tue, 19 Aug 2025 08:50:25 +0530	[thread overview]
Message-ID: <87bjocatfq.fsf@gmail.com> (raw)
In-Reply-To: <20250813122319.62278-1-gautam@linux.ibm.com>

Gautam Menghani <gautam@linux.ibm.com> writes:

> Remove duplicate definition of ppc_msgsnd_sync() introduced in commit
> b87ac0218355 ('powerpc: Introduce msgsnd/doorbell barrier primitives').
>
> No functional change intended.
>

Earlier this function was duplicated at 2 places i.e. in
#ifdef CONFIG_PPC_BOOK3S and #else block. This patch takes those
duplicate definitions out and move it to a common place.

BTW, there is nothing sndmsg specific in this, so this could be open
coded as well. But as far as this patch is concerned, it looks good.

So please feel free to add:
Reviewed-by: Ritesh Harjani (IBM) <riteshh@linux.ibm.com>


> Signed-off-by: Gautam Menghani <gautam@linux.ibm.com>
> ---
>  arch/powerpc/include/asm/dbell.h | 18 ++++++------------
>  1 file changed, 6 insertions(+), 12 deletions(-)
>
> diff --git a/arch/powerpc/include/asm/dbell.h b/arch/powerpc/include/asm/dbell.h
> index 3e9da22a2779..0b9ef726f92c 100644
> --- a/arch/powerpc/include/asm/dbell.h
> +++ b/arch/powerpc/include/asm/dbell.h
> @@ -40,12 +40,6 @@ static inline void _ppc_msgsnd(u32 msg)
>  				: : "i" (CPU_FTR_HVMODE), "r" (msg));
>  }
>  
> -/* sync before sending message */
> -static inline void ppc_msgsnd_sync(void)
> -{
> -	__asm__ __volatile__ ("sync" : : : "memory");
> -}
> -
>  /* sync after taking message interrupt */
>  static inline void ppc_msgsync(void)
>  {
> @@ -76,12 +70,6 @@ static inline void _ppc_msgsnd(u32 msg)
>  	__asm__ __volatile__ (PPC_MSGSND(%0) : : "r" (msg));
>  }
>  
> -/* sync before sending message */
> -static inline void ppc_msgsnd_sync(void)
> -{
> -	__asm__ __volatile__ ("sync" : : : "memory");
> -}
> -
>  /* sync after taking message interrupt */
>  static inline void ppc_msgsync(void)
>  {
> @@ -91,6 +79,12 @@ static inline void ppc_msgsync(void)
>  
>  extern void doorbell_exception(struct pt_regs *regs);
>  
> +/* sync before sending message */
> +static inline void ppc_msgsnd_sync(void)
> +{
> +	__asm__ __volatile__ ("sync" : : : "memory");
> +}
> +
>  static inline void ppc_msgsnd(enum ppc_dbell type, u32 flags, u32 tag)
>  {
>  	u32 msg = PPC_DBELL_TYPE(type) | (flags & PPC_DBELL_MSG_BRDCAST) |
> -- 
> 2.50.1


  reply	other threads:[~2025-08-19  3:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-13 12:23 [PATCH] powerpc: Remove duplicate definition for ppc_msgsnd_sync() Gautam Menghani
2025-08-19  3:20 ` Ritesh Harjani [this message]
2025-09-12  3:56 ` Madhavan Srinivasan

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=87bjocatfq.fsf@gmail.com \
    --to=riteshh@linux.ibm.com \
    --cc=christophe.leroy@csgroup.eu \
    --cc=gautam@linux.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mpe@ellerman.id.au \
    --cc=npiggin@gmail.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).