From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org, Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"David S . Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>,
Mike Rapoport <rppt@kernel.org>,
kernel-team@android.com
Subject: [PATCH 0/3] sparc32 SRMMU fixes for SMP
Date: Tue, 26 May 2020 17:32:59 +0000 [thread overview]
Message-ID: <20200526173302.377-1-will@kernel.org> (raw)
Hi folks,
Enabling SMP for sparc32 uncovered some issues in the SRMMU page-table
allocation code. One of these was introduced by me, but the other two
seem to have been there a while and are probably just exposed more
easily by my recent changes.
Tested on QEMU. I'm assuming these will go via David's tree.
Cheers,
Will
--->8
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: David S. Miller <davem@davemloft.net>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: kernel-team@android.com
Will Deacon (3):
sparc32: mm: Don't try to free page-table pages if ctor() fails
sparc32: mm: Disable SPLIT_PTLOCK_CPUS
sparc32: mm: Only call ctor()/dtor() functions for first and last user
arch/sparc/mm/srmmu.c | 15 +++++++++++----
mm/Kconfig | 4 ++++
2 files changed, 15 insertions(+), 4 deletions(-)
--
2.27.0.rc0.183.gde8f92d652-goog
WARNING: multiple messages have this Message-ID (diff)
From: Will Deacon <will@kernel.org>
To: linux-kernel@vger.kernel.org
Cc: sparclinux@vger.kernel.org, Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
"David S . Miller" <davem@davemloft.net>,
Guenter Roeck <linux@roeck-us.net>,
Mike Rapoport <rppt@kernel.org>,
kernel-team@android.com
Subject: [PATCH 0/3] sparc32 SRMMU fixes for SMP
Date: Tue, 26 May 2020 18:32:59 +0100 [thread overview]
Message-ID: <20200526173302.377-1-will@kernel.org> (raw)
Hi folks,
Enabling SMP for sparc32 uncovered some issues in the SRMMU page-table
allocation code. One of these was introduced by me, but the other two
seem to have been there a while and are probably just exposed more
easily by my recent changes.
Tested on QEMU. I'm assuming these will go via David's tree.
Cheers,
Will
--->8
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: David S. Miller <davem@davemloft.net>
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Mike Rapoport <rppt@kernel.org>
Cc: kernel-team@android.com
Will Deacon (3):
sparc32: mm: Don't try to free page-table pages if ctor() fails
sparc32: mm: Disable SPLIT_PTLOCK_CPUS
sparc32: mm: Only call ctor()/dtor() functions for first and last user
arch/sparc/mm/srmmu.c | 15 +++++++++++----
mm/Kconfig | 4 ++++
2 files changed, 15 insertions(+), 4 deletions(-)
--
2.27.0.rc0.183.gde8f92d652-goog
next reply other threads:[~2020-05-26 17:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 17:32 Will Deacon [this message]
2020-05-26 17:32 ` [PATCH 0/3] sparc32 SRMMU fixes for SMP Will Deacon
2020-05-26 17:33 ` [PATCH 1/3] sparc32: mm: Don't try to free page-table pages if ctor() fails Will Deacon
2020-05-26 17:33 ` Will Deacon
2020-05-26 17:33 ` [PATCH 2/3] sparc32: mm: Disable SPLIT_PTLOCK_CPUS Will Deacon
2020-05-26 17:33 ` Will Deacon
2020-05-26 17:33 ` [PATCH 3/3] sparc32: mm: Only call ctor()/dtor() functions for first and last user Will Deacon
2020-05-26 17:33 ` Will Deacon
2020-06-03 1:46 ` [PATCH 0/3] sparc32 SRMMU fixes for SMP David Miller
2020-06-03 1:46 ` David Miller
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=20200526173302.377-1-will@kernel.org \
--to=will@kernel.org \
--cc=davem@davemloft.net \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=peterz@infradead.org \
--cc=rppt@kernel.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.