From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel Development <linux-kernel@vger.kernel.org>,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH 547] M68k: Add missing pieces of thread info TIF_MEMDIE support
Date: Mon, 21 Mar 2005 21:25:51 +0100 [thread overview]
Message-ID: <200503212025.j2LKPpUt011337@anakin.of.borg> (raw)
M68k: Add missing pieces of thread info TIF_MEMDIE support (introduced in
2.6.11-rc3)
Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>
--- linux-2.6.12-rc1/include/asm-m68k/processor.h 2004-04-30 17:54:35.000000000 +0200
+++ linux-m68k-2.6.12-rc1/include/asm-m68k/processor.h 2005-03-20 11:57:32.743537879 +0100
@@ -63,7 +63,8 @@ struct task_work {
char need_resched;
unsigned char delayed_trace; /* single step a syscall */
unsigned char syscall_trace; /* count of syscall interceptors */
- unsigned char pad[3];
+ unsigned char memdie; /* task was selected to be killed */
+ unsigned char pad[2];
};
struct thread_struct {
--- linux-2.6.12-rc1/include/asm-m68k/thread_info.h 2005-02-03 15:05:36.000000000 +0100
+++ linux-m68k-2.6.12-rc1/include/asm-m68k/thread_info.h 2005-02-04 13:20:27.000000000 +0100
@@ -70,6 +70,9 @@ extern int thread_flag_fixme(void);
case TIF_SYSCALL_TRACE: \
tsk->thread.work.syscall_trace = val; \
break; \
+ case TIF_MEMDIE: \
+ tsk->thread.work.memdie = val; \
+ break; \
default: \
thread_flag_fixme(); \
} \
@@ -87,6 +90,9 @@ extern int thread_flag_fixme(void);
case TIF_SYSCALL_TRACE: \
___res = tsk->thread.work.syscall_trace;\
break; \
+ case TIF_MEMDIE: \
+ ___res = tsk->thread.work.memdie;\
+ break; \
default: \
___res = thread_flag_fixme(); \
} \
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
reply other threads:[~2005-03-21 20:33 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=200503212025.j2LKPpUt011337@anakin.of.borg \
--to=geert@linux-m68k.org \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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
all inboxes | Powered by JetHome®