All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Schnelle <svens@stackframe.org>
To: deller@gmx.de
Cc: linux-parisc@vger.kernel.org
Subject: [PATCH 0/4] parisc: fixes for CONFIG_PREEMPT
Date: Fri,  8 Oct 2021 22:48:22 +0200	[thread overview]
Message-ID: <20211008204825.6229-1-svens@stackframe.org> (raw)

Out of curiosity i enabled CONFIG_PREEMPT on my c8000. The kernel didn't
even compile. After fixing compilation i noticed a lot of segmentation
faults - usually a few processes crashed already at boot, with sshd the
most notable one. Most of the time the processes where crashing with a
DTLB or ITLB miss.

With these fixes, i was able to compile a linux kernel on the c8000
with preemption enabled without crashes.

Sven Schnelle (4):
  parisc: disable preemption during local tlb flush
  parisc: fix preempt_count() check in entry.S
  parisc: disable preemption in send_IPI_allbutself()
  parisc: fix warning in flush_tlb_all

 arch/parisc/kernel/cache.c | 3 +++
 arch/parisc/kernel/entry.S | 5 +++--
 arch/parisc/kernel/smp.c   | 3 ++-
 arch/parisc/mm/init.c      | 4 ++--
 4 files changed, 10 insertions(+), 5 deletions(-)

-- 
2.33.0


             reply	other threads:[~2021-10-08 20:48 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-08 20:48 Sven Schnelle [this message]
2021-10-08 20:48 ` [PATCH 1/4] parisc: disable preemption during local tlb flush Sven Schnelle
2021-10-08 21:35   ` Sven Schnelle
2021-10-09 12:30     ` Helge Deller
2021-10-08 20:48 ` [PATCH 2/4] parisc: fix preempt_count() check in entry.S Sven Schnelle
2021-10-08 20:48 ` [PATCH 3/4] parisc: disable preemption in send_IPI_allbutself() Sven Schnelle
2021-10-08 20:48 ` [PATCH 4/4] parisc: fix warning in flush_tlb_all Sven Schnelle

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=20211008204825.6229-1-svens@stackframe.org \
    --to=svens@stackframe.org \
    --cc=deller@gmx.de \
    --cc=linux-parisc@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.