From: David Miller <davem@davemloft.net>
To: npiggin@gmail.com
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org, aneesh.kumar@linux.ibm.com,
akpm@linux-foundation.org, axboe@kernel.dk, peterz@infradead.org
Subject: Re: [PATCH v2 3/4] sparc64: remove mm_cpumask clearing to fix kthread_use_mm race
Date: Mon, 14 Sep 2020 12:59:42 -0700 (PDT) [thread overview]
Message-ID: <20200914.125942.5644261129883859.davem@davemloft.net> (raw)
In-Reply-To: <20200914045219.3736466-4-npiggin@gmail.com>
From: Nicholas Piggin <npiggin@gmail.com>
Date: Mon, 14 Sep 2020 14:52:18 +1000
...
> The basic fix for sparc64 is to remove its mm_cpumask clearing code. The
> optimisation could be effectively restored by sending IPIs to mm_cpumask
> members and having them remove themselves from mm_cpumask. This is more
> tricky so I leave it as an exercise for someone with a sparc64 SMP.
> powerpc has a (currently similarly broken) example.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Sad to see this optimization go away, but what can I do:
Acked-by: David S. Miller <davem@davemloft.net>
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: npiggin@gmail.com
Cc: linux-mm@kvack.org, linux-arch@vger.kernel.org,
linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
sparclinux@vger.kernel.org, aneesh.kumar@linux.ibm.com,
akpm@linux-foundation.org, axboe@kernel.dk, peterz@infradead.org
Subject: Re: [PATCH v2 3/4] sparc64: remove mm_cpumask clearing to fix kthread_use_mm race
Date: Mon, 14 Sep 2020 19:59:42 +0000 [thread overview]
Message-ID: <20200914.125942.5644261129883859.davem@davemloft.net> (raw)
In-Reply-To: <20200914045219.3736466-4-npiggin@gmail.com>
From: Nicholas Piggin <npiggin@gmail.com>
Date: Mon, 14 Sep 2020 14:52:18 +1000
...
> The basic fix for sparc64 is to remove its mm_cpumask clearing code. The
> optimisation could be effectively restored by sending IPIs to mm_cpumask
> members and having them remove themselves from mm_cpumask. This is more
> tricky so I leave it as an exercise for someone with a sparc64 SMP.
> powerpc has a (currently similarly broken) example.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Sad to see this optimization go away, but what can I do:
Acked-by: David S. Miller <davem@davemloft.net>
WARNING: multiple messages have this Message-ID (diff)
From: David Miller <davem@davemloft.net>
To: npiggin@gmail.com
Cc: linux-arch@vger.kernel.org, axboe@kernel.dk,
peterz@infradead.org, aneesh.kumar@linux.ibm.com,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
sparclinux@vger.kernel.org, akpm@linux-foundation.org,
linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH v2 3/4] sparc64: remove mm_cpumask clearing to fix kthread_use_mm race
Date: Mon, 14 Sep 2020 12:59:42 -0700 (PDT) [thread overview]
Message-ID: <20200914.125942.5644261129883859.davem@davemloft.net> (raw)
In-Reply-To: <20200914045219.3736466-4-npiggin@gmail.com>
From: Nicholas Piggin <npiggin@gmail.com>
Date: Mon, 14 Sep 2020 14:52:18 +1000
...
> The basic fix for sparc64 is to remove its mm_cpumask clearing code. The
> optimisation could be effectively restored by sending IPIs to mm_cpumask
> members and having them remove themselves from mm_cpumask. This is more
> tricky so I leave it as an exercise for someone with a sparc64 SMP.
> powerpc has a (currently similarly broken) example.
>
> Signed-off-by: Nicholas Piggin <npiggin@gmail.com>
Sad to see this optimization go away, but what can I do:
Acked-by: David S. Miller <davem@davemloft.net>
next prev parent reply other threads:[~2020-09-14 20:00 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-14 4:52 [PATCH v2 0/4] more mm switching vs TLB shootdown and lazy tlb fixes Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` [PATCH v2 1/4] mm: fix exec activate_mm vs TLB shootdown and lazy tlb switching race Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 10:56 ` peterz
2020-09-14 10:56 ` peterz
2020-09-14 10:56 ` peterz
2020-09-15 2:48 ` Nicholas Piggin
2020-09-15 2:48 ` Nicholas Piggin
2020-09-15 2:48 ` Nicholas Piggin
2020-09-15 11:26 ` Michael Ellerman
2020-09-15 11:26 ` Michael Ellerman
2020-09-15 11:26 ` Michael Ellerman
2020-09-18 12:18 ` Michael Ellerman
2020-09-18 12:18 ` Michael Ellerman
2020-09-18 12:18 ` Michael Ellerman
2020-09-14 4:52 ` [PATCH v2 2/4] powerpc: select ARCH_WANT_IRQS_OFF_ACTIVATE_MM Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` [PATCH v2 3/4] sparc64: remove mm_cpumask clearing to fix kthread_use_mm race Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 7:00 ` Nicholas Piggin
2020-09-14 7:00 ` Nicholas Piggin
2020-09-14 7:00 ` Nicholas Piggin
2020-09-14 10:23 ` Anatoly Pugachev
2020-09-14 10:23 ` Anatoly Pugachev
2020-09-14 10:23 ` Anatoly Pugachev
2020-09-14 10:23 ` Anatoly Pugachev
2020-09-15 2:49 ` Nicholas Piggin
2020-09-15 2:49 ` Nicholas Piggin
2020-09-15 2:49 ` Nicholas Piggin
2020-09-14 19:59 ` David Miller [this message]
2020-09-14 19:59 ` David Miller
2020-09-14 19:59 ` David Miller
2020-09-15 3:24 ` Nicholas Piggin
2020-09-15 3:24 ` Nicholas Piggin
2020-09-15 3:24 ` Nicholas Piggin
2020-09-15 19:42 ` David Miller
2020-09-15 19:42 ` David Miller
2020-09-15 19:42 ` David Miller
2020-09-14 4:52 ` [PATCH v2 4/4] powerpc/64s/radix: Fix mm_cpumask trimming race vs kthread_use_mm Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-14 4:52 ` Nicholas Piggin
2020-09-24 12:28 ` [PATCH v2 0/4] more mm switching vs TLB shootdown and lazy tlb fixes Michael Ellerman
2020-09-24 12:28 ` Michael Ellerman
2020-09-24 12:28 ` Michael Ellerman
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=20200914.125942.5644261129883859.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@linux.ibm.com \
--cc=axboe@kernel.dk \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=npiggin@gmail.com \
--cc=peterz@infradead.org \
--cc=sparclinux@vger.kernel.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.