All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jiaxun Yang <jiaxun.yang@flygoat.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	Huacai Chen <chenhuacai@kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>,
	Serge Semin <fancer.lancer@gmail.com>,
	Paul Burton <paulburton@kernel.org>,
	linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 02/10] MIPS: smp: Manage IPI interrupts as percpu_devid interrupts
Date: Wed, 3 Jul 2024 17:03:45 +0200	[thread overview]
Message-ID: <ZoVoUabfZiiAXWKR@alpha.franken.de> (raw)
In-Reply-To: <20240616-b4-mips-ipi-improvements-v1-2-e332687f1692@flygoat.com>

On Sun, Jun 16, 2024 at 10:03:06PM +0100, Jiaxun Yang wrote:
> IPI interrupts need to be enabled when a new CPU coming up.
> 
> Manage them as percpu_devid interrupts and invoke enable/disable
> functions at appropriate time to perform enabling as required,
> similar to what RISC-V and Arm doing.
> 
> Signed-off-by: Jiaxun Yang <jiaxun.yang@flygoat.com>
> ---
>  arch/mips/include/asm/ipi.h | 11 +++++++++++
>  arch/mips/kernel/smp.c      | 26 ++++++++++++++++++++++++--
>  2 files changed, 35 insertions(+), 2 deletions(-)
> 
> diff --git a/arch/mips/include/asm/ipi.h b/arch/mips/include/asm/ipi.h
> index df7a0ac4227a..88b507339f51 100644
> --- a/arch/mips/include/asm/ipi.h
> +++ b/arch/mips/include/asm/ipi.h
> @@ -29,6 +29,17 @@ int mips_smp_ipi_allocate(const struct cpumask *mask);
>   * Return 0 on success.
>   */
>  int mips_smp_ipi_free(const struct cpumask *mask);
> +
> +void mips_smp_ipi_enable(void);
> +void mips_smp_ipi_disable(void);
> +#else
> +static inline void mips_smp_ipi_enable(void)
> +{
> +}
> +
> +static inline void mips_smp_ipi_disable(void)
> +{
> +}
>  #endif /* CONFIG_GENERIC_IRQ_IPI */
>  #endif /* CONFIG_SMP */
>  #endif
> diff --git a/arch/mips/kernel/smp.c b/arch/mips/kernel/smp.c
> index a6cf6444533e..710644d47106 100644
> --- a/arch/mips/kernel/smp.c
> +++ b/arch/mips/kernel/smp.c
> @@ -186,6 +186,7 @@ irq_handler_t ipi_handlers[IPI_MAX] __read_mostly = {
>  };
>  
>  #ifdef CONFIG_GENERIC_IRQ_IPI
> +static DEFINE_PER_CPU_READ_MOSTLY(int, ipi_dummy_dev);
>  static int ipi_virqs[IPI_MAX] __ro_after_init;
>  static struct irq_desc *ipi_desc[IPI_MAX] __read_mostly;
>  
> @@ -225,13 +226,29 @@ void mips_smp_send_ipi_mask(const struct cpumask *mask,
>  	local_irq_restore(flags);
>  }
>  
> +void mips_smp_ipi_enable(void)
> +{
> +	int i;
> +
> +	for (i = 0; i < IPI_MAX; i++)
> +		enable_percpu_irq(ipi_virqs[i], IRQ_TYPE_NONE);
> +}
> +
> +void mips_smp_ipi_disable(void)
> +{
> +	int i;
> +
> +	for (i = 0; i < IPI_MAX; i++)
> +		disable_percpu_irq(ipi_virqs[i]);
> +}
> +

there is no user of mips_smp_ipi_disable() (at least I didn't see one),
so do we need this patch at all ? Just looking like ARM or RiscV isn't
a justification for code churn.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2024-07-03 15:13 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-16 21:03 [PATCH 00/10] MIPS: IPI Improvements Jiaxun Yang
2024-06-16 21:03 ` [PATCH 01/10] MIPS: smp: Make IPI interrupts scalable Jiaxun Yang
2024-07-03 15:04   ` Thomas Bogendoerfer
2024-07-03 20:15     ` Jiaxun Yang
2024-07-03 21:26       ` Maciej W. Rozycki
2024-07-03 22:07         ` Jiaxun Yang
2024-07-04 14:34           ` Florian Fainelli
2024-07-04 22:36           ` Maciej W. Rozycki
2024-07-05  6:55             ` Thomas Bogendoerfer
2024-07-04 13:14       ` Thomas Bogendoerfer
2024-07-05  8:40     ` Serge Semin
2024-07-05  9:08       ` Jiaxun Yang
2024-06-16 21:03 ` [PATCH 02/10] MIPS: smp: Manage IPI interrupts as percpu_devid interrupts Jiaxun Yang
2024-07-03 15:03   ` Thomas Bogendoerfer [this message]
2024-07-03 20:08     ` Jiaxun Yang
2024-07-04 13:05       ` Thomas Bogendoerfer
2024-06-16 21:03 ` [PATCH 03/10] MIPS: smp: Provide platform IPI virq & domain hooks Jiaxun Yang
2024-06-16 21:03 ` [PATCH 04/10] MIPS: Move mips_smp_ipi_init call after prepare_cpus Jiaxun Yang
2024-06-17 13:53   ` Huacai Chen
2024-06-17 22:10     ` Jiaxun Yang
2024-06-18  3:51       ` Huacai Chen
2024-06-18 14:50         ` Jiaxun Yang
2024-07-03 15:09           ` Thomas Bogendoerfer
2024-06-16 21:03 ` [PATCH 05/10] MIPS: smp: Implement IPI stats Jiaxun Yang
2024-07-03 15:11   ` Thomas Bogendoerfer
2024-06-16 21:03 ` [PATCH 06/10] irqchip: irq-mips-gic: Switch to ipi_mux Jiaxun Yang
2024-06-16 21:03 ` [PATCH 07/10] MIPS: Implement get_mips_sw_int hook Jiaxun Yang
2024-06-16 21:03 ` [PATCH 08/10] MIPS: GIC: Implement get_sw_int hook Jiaxun Yang
2024-06-16 21:03 ` [PATCH 09/10] irqchip: irq-mips-cpu: Rework software IRQ handling flow Jiaxun Yang
2024-06-16 21:03 ` [PATCH 10/10] MIPS: smp-mt: Rework IPI functions Jiaxun Yang
2024-07-03  8:37 ` [PATCH 00/10] MIPS: IPI Improvements Jiaxun Yang

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=ZoVoUabfZiiAXWKR@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=chenhuacai@kernel.org \
    --cc=fancer.lancer@gmail.com \
    --cc=florian.fainelli@broadcom.com \
    --cc=jiaxun.yang@flygoat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mips@vger.kernel.org \
    --cc=paulburton@kernel.org \
    --cc=tglx@linutronix.de \
    /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.