linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Christopher M. Riedl" <cmr@informatik.wtf>
To: linuxppc-dev@ozlabs.org
Cc: "Christopher M. Riedl" <cmr@informatik.wtf>, ajd@linux.ibm.com
Subject: [PATCH 0/3] Fix oops in shared-processor spinlocks
Date: Sun, 28 Jul 2019 07:54:35 -0500	[thread overview]
Message-ID: <20190728125438.1550-1-cmr@informatik.wtf> (raw)

Fixes an oops when calling the shared-processor spinlock implementation
from a non-SP LPAR. Also take this opportunity to refactor
SHARED_PROCESSOR a bit.

Reference:  https://github.com/linuxppc/issues/issues/229

Christopher M. Riedl (3):
  powerpc/spinlocks: Refactor SHARED_PROCESSOR
  powerpc/spinlocks: Rename SPLPAR-only spinlocks
  powerpc/spinlocks: Fix oops in shared-processor spinlocks

 arch/powerpc/include/asm/spinlock.h | 59 ++++++++++++++++++++---------
 arch/powerpc/lib/locks.c            |  6 +--
 2 files changed, 45 insertions(+), 20 deletions(-)

-- 
2.22.0


             reply	other threads:[~2019-07-28 13:03 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-28 12:54 Christopher M. Riedl [this message]
2019-07-28 12:54 ` [PATCH 1/3] powerpc/spinlocks: Refactor SHARED_PROCESSOR Christopher M. Riedl
2019-07-30 21:31   ` Thiago Jung Bauermann
2019-07-30 23:31     ` Christopher M Riedl
2019-07-31  0:11       ` Thiago Jung Bauermann
2019-07-31  2:36         ` Christopher M Riedl
2019-08-01  3:20   ` Andrew Donnellan
2019-07-28 12:54 ` [PATCH 2/3] powerpc/spinlocks: Rename SPLPAR-only spinlocks Christopher M. Riedl
2019-08-01  3:27   ` Andrew Donnellan
2019-07-28 12:54 ` [PATCH 3/3] powerpc/spinlock: Fix oops in shared-processor spinlocks Christopher M. Riedl
2019-08-01  3:33   ` Andrew Donnellan

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=20190728125438.1550-1-cmr@informatik.wtf \
    --to=cmr@informatik.wtf \
    --cc=ajd@linux.ibm.com \
    --cc=linuxppc-dev@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 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).