MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-ID: <19205.28811.911525.832480@pilspetsen.it.uu.se>
Date: Thu, 19 Nov 2009 17:21:31 +0100
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?
In-Reply-To: <10f740e80911181202l6cca6b41m827f2c51f639d1f0@mail.gmail.com>
References: <10f740e80911181202l6cca6b41m827f2c51f639d1f0@mail.gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1126
Lines: 22

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.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/