From: Michael Schmitz <schmitzmic@gmail.com>
To: linux-m68k@vger.kernel.org
Cc: geert@linux-m68k.org, uli@fpond.eu, fthain@linux-m68k.org,
viro@zeniv.linux.org.uk
Subject: [PATCH RFC v2 0/8] m68k v4.4 backport fixes
Date: Mon, 5 Feb 2024 15:32:28 +1300 [thread overview]
Message-ID: <20240205023236.9325-1-schmitzmic@gmail.com> (raw)
CIP v4.4 backport patches for m68k. Basically everything needed
to make v4.4 work on my Falcon. This includes my iounmap() fix,
Al Viro's signal handling and uaccess page fault fixes, my 030
buserr_c fix for exception handling during page faults, and Finn's
030 signal frame fix.
Patch 1 should be applied to v4.4-cip, or else ioremap / iounmap
has no chance to work on 030 processors.
Patches 2 and 3 have been applied to v4.4-cip.
Patches 4-6 are a prerequisite for patch 8, Finn Thain's 'm68k:
Move signal frame following exception on 68020/030' patch which
had been applied but failed to compile (see error reported in
https://lore.kernel.org/oe-kbuild-all/202401310920.sBSI4BHj-lkp@intel.com/
which has gone away with patches 4-6 in place).
Patch 7 is another page fault handling fix which should be applied
(though I have found no test case for it, and cannot say how common
that livelock issue is on m68k).
All patches as RFC version to give Geert and Al a chance to yell
at me in case I got details of these patches wrong. I don't claim
to understand signal handling in anywhere near the required level
of detail.
Tested on my 68030 Atari Falcon.
Cheers,
Michael
next reply other threads:[~2024-02-05 2:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 2:32 Michael Schmitz [this message]
2024-02-05 2:32 ` [PATCH RFC v2 1/8] m68k/mm: Adjust VM area to be unmapped by gap size for __iounmap() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 2/8] m68k: Only force 030 bus error if PC not in exception table Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 3/8] m68k: include module.h to make use of exception handling in traps.c Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 4/8] m68k: Handle arrivals of multiple signals correctly Michael Schmitz
2024-02-05 8:10 ` Geert Uytterhoeven
2024-02-05 10:15 ` Michael Schmitz
2024-02-08 11:53 ` Ulrich Hecht
2024-02-08 22:51 ` Finn Thain
2024-02-12 0:48 ` Michael Schmitz
2024-02-12 10:02 ` Ulrich Hecht
2024-02-13 5:05 ` Finn Thain
2024-02-05 2:32 ` [PATCH RFC v2 5/8] m68k: Update ->thread.esp0 before calling syscall_trace() in ret_from_signal Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 6/8] m68k: Leave stack mangling to asm wrapper of sigreturn() Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 7/8] m68k: fix livelock in uaccess Michael Schmitz
2024-02-05 2:32 ` [PATCH RFC v2 8/8] m68k: Move signal frame following exception on 68020/030 Michael Schmitz
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=20240205023236.9325-1-schmitzmic@gmail.com \
--to=schmitzmic@gmail.com \
--cc=fthain@linux-m68k.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uli@fpond.eu \
--cc=viro@zeniv.linux.org.uk \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).