All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nicholas Piggin" <npiggin@gmail.com>
To: "Paul Mackerras" <paulus@ozlabs.org>
Cc: <linuxppc-dev@lists.ozlabs.org>
Subject: Re: [PATCH 4/5] powerpc: Define config option for processors without broadcast TLBIE
Date: Wed, 29 Jan 2025 18:17:00 +1000	[thread overview]
Message-ID: <D7EEPV6CFJO1.28GHITX47M9FB@gmail.com> (raw)
In-Reply-To: <Z5nUc54yZDqGqr0P@thinks.paulus.ozlabs.org>

On Wed Jan 29, 2025 at 5:10 PM AEST, Paul Mackerras wrote:
> On Wed, Jan 29, 2025 at 04:14:25PM +1000, Nicholas Piggin wrote:
>> On Wed Jan 29, 2025 at 8:53 AM AEST, Paul Mackerras wrote:
>> > Power ISA v3.1 implementations in the Linux Compliancy Subset and
>> > lower are not required to implement broadcast TLBIE, and in fact
>> > Microwatt doesn't.  To avoid the need to specify "disable_tlbie" on
>> > the kernel command line on SMP Microwatt systems, this defines a
>> > config option that asserts that broadcast TLBIE should never be used
>> > (the kernel will instead use IPIs to trigger local TLBIEs on other
>> > CPUs when required).
>> >
>> > Signed-off-by: Paul Mackerras <paulus@ozlabs.org>
>> > ---
>> >  arch/powerpc/mm/book3s64/pgtable.c       | 10 ++++++++--
>> >  arch/powerpc/platforms/Kconfig.cputype   | 12 ++++++++++++
>> >  arch/powerpc/platforms/microwatt/Kconfig |  1 +
>> >  3 files changed, 21 insertions(+), 2 deletions(-)
>> >
>> > diff --git a/arch/powerpc/mm/book3s64/pgtable.c b/arch/powerpc/mm/book3s64/pgtable.c
>> > index 374542528080..14ee96e2a581 100644
>> > --- a/arch/powerpc/mm/book3s64/pgtable.c
>> > +++ b/arch/powerpc/mm/book3s64/pgtable.c
>> > @@ -588,10 +588,16 @@ int pmd_move_must_withdraw(struct spinlock *new_pmd_ptl,
>> >  }
>> >  #endif
>> >  
>> > +#ifndef CONFIG_PPC_RADIX_NO_BROADCAST_TLBIE
>> 
>> Hate to bikeshed, but would it be annoying to make this an affirmative
>> option?
>
> I guess we'd have to make all the platforms that do have broadcast
> tlbie (and a book3s-64 MMU with radix) select that option.  Which
> would be powernv and pseries, I would think.  If that's correct then
> it's probably not too annoying.  Should I do that in v2?

I think you're right, powernv and pseries. If you wouldn't mind doing
it please.

Thanks,
Nick


  reply	other threads:[~2025-01-29  8:17 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-28 22:49 [PATCH 0/5] Microwatt updates Paul Mackerras
2025-01-28 22:51 ` [PATCH 1/5] powerpc/microwatt: Select COMMON_CLK in order to get the clock framework Paul Mackerras
2025-01-29  5:57   ` Nicholas Piggin
2025-01-28 22:52 ` [PATCH 2/5] powerpc/microwatt: Device-tree updates Paul Mackerras
2025-01-29  6:36   ` Nicholas Piggin
2025-01-29  7:18     ` Paul Mackerras
2025-01-29  8:20       ` Nicholas Piggin
2025-01-31 17:03         ` Segher Boessenkool
2025-01-31 16:55       ` Segher Boessenkool
2025-01-31 16:53     ` Segher Boessenkool
2025-01-31 16:48   ` Segher Boessenkool
2025-01-28 22:52 ` [PATCH 3/5] powerpc/microwatt: Define an idle power-save function Paul Mackerras
2025-01-29  6:06   ` Nicholas Piggin
2025-01-29  6:49     ` Paul Mackerras
2025-01-31 16:32     ` Segher Boessenkool
2025-02-01  1:41       ` Paul Mackerras
2025-01-31 16:25   ` Segher Boessenkool
2025-01-28 22:53 ` [PATCH 4/5] powerpc: Define config option for processors without broadcast TLBIE Paul Mackerras
2025-01-29  6:14   ` Nicholas Piggin
2025-01-29  7:10     ` Paul Mackerras
2025-01-29  8:17       ` Nicholas Piggin [this message]
2025-01-31 17:30       ` Segher Boessenkool
2025-01-31 17:26   ` Segher Boessenkool
2025-01-28 22:55 ` [PATCH 5/5] powerpc/microwatt: Add SMP support Paul Mackerras
2025-01-29  6:21   ` Nicholas Piggin
2025-01-29  6:57     ` Paul Mackerras
2025-01-29  8:12       ` Nicholas Piggin
2025-01-31  1:27         ` Paul Mackerras
2025-01-29 12:50       ` Michael Ellerman
2025-01-31  1:34         ` Paul Mackerras
2025-01-31 16:13 ` [PATCH 0/5] Microwatt updates Segher Boessenkool
2025-02-01  1:22   ` Paul Mackerras
2025-03-02 10:13     ` Gabriel Paubert

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=D7EEPV6CFJO1.28GHITX47M9FB@gmail.com \
    --to=npiggin@gmail.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=paulus@ozlabs.org \
    /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.