From: Mikael Pettersson <mikpe@it.uu.se>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k <linux-m68k@vger.kernel.org>,
uClinux development list <uclinux-dev@uclinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: TIF_NOTIFY_RESUME on m68k?
Date: Thu, 19 Nov 2009 17:21:31 +0100 [thread overview]
Message-ID: <19205.28811.911525.832480@pilspetsen.it.uu.se> (raw)
In-Reply-To: <10f740e80911181202l6cca6b41m827f2c51f639d1f0@mail.gmail.com>
Geert Uytterhoeven writes:
> Has anyone already looked into TIF_NOTIFY_RESUME support for m68k?
You need to change your entry.S code where it now does single-bit tests
for TIF_SIGPENDING with lsl/jmi do_signal_return, to instead test a 2-bit
(or larger, it that gives better code) flag field for zero/non-zero.
TIF_SIGPENDING and TIF_NOTIFY_RESUME should be alone in that field.
In the non-zero case you should call a new do_notify_resume() written in C,
which will then test TIF_SIGPENDING and TIF_NOTIFY_RESUME just like many
other archs do.
BTW, m68k also lacks TIF_RESTORE_SIGMASK support. You could probably use
the one I added to ARM very recently as a model.
Do current 2.6.3x m68k kernels boot on aranym? Last time I tried aranym
it could only boot som ancient hacked 2.4 kernel, for 2.6 kernels I got
disk detection errors due to what looked like byteswapping issues.
next prev parent reply other threads:[~2009-11-19 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-18 20:02 TIF_NOTIFY_RESUME on m68k? Geert Uytterhoeven
2009-11-18 23:25 ` [uClinux-dev] " David Howells
2009-11-19 16:21 ` Mikael Pettersson [this message]
2009-11-19 16:34 ` Andreas Schwab
2009-11-22 7:05 ` 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=19205.28811.911525.832480@pilspetsen.it.uu.se \
--to=mikpe@it.uu.se \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=uclinux-dev@uclinux.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