From: randy_dunlap <rdunlap@xenotime.net>
To: Roman Zippel <zippel@linux-m68k.org>
Cc: viro@parcelfarce.linux.theplanet.co.uk, geert@linux-m68k.org,
linux-kernel@vger.kernel.org, linux-m68k@vger.kernel.org
Subject: Re: more thread_info patches
Date: Tue, 31 May 2005 08:37:59 -0700 [thread overview]
Message-ID: <20050531083759.320ccb5a.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0505311127330.3728@scrub.home>
On Tue, 31 May 2005 11:35:04 +0200 (CEST) Roman Zippel wrote:
| Hi,
|
| On Mon, 30 May 2005, randy_dunlap wrote:
|
| > | Index: linux-2.6-mm/include/linux/sched.h
| > | ===================================================================
| > | --- linux-2.6-mm.orig/include/linux/sched.h 2005-05-31 01:19:01.636591190 +0200
| > | +++ linux-2.6-mm/include/linux/sched.h 2005-05-31 01:19:05.913856451 +0200
| > | @@ -617,6 +617,7 @@ struct mempolicy;
| > | struct task_struct {
| > | volatile long state; /* -1 unrunnable, 0 runnable, >0 stopped */
| > | struct thread_info *thread_info;
| > | + void *stack;
| >
| > Any reason this is void * instead of being more strongly typed?
| > Does the actual type vary?
|
| Yes, on m68k it actually doesn't point to the thread_info at all.
| The point of these patches are to allow archs to put the thread_info
| structure somewhere else. Archs with a thread register can keep
| task_struct and thread_info together and directly accessable via the
| thread register. Only because i386 has no usable thread register, doesn't
| mean everyone else has to suffer.
I see, thanks for the explanation.
| > And a general comments about the 4 emails:
| > they all have the same subject. :(
|
| I know and I did this intentionally, as these patches were not intended to
| be applied, they are based on Al's patches and even these aren't in -mm
| yet. I maybe should have added a [RFC].
I agree.
Thanks,
---
~Randy
next prev parent reply other threads:[~2005-05-31 15:38 UTC|newest]
Thread overview: 85+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 0:59 Linux 2.6.12-rc3 Linus Torvalds
2005-04-21 1:09 ` Alejandro Bonilla
2005-04-21 1:26 ` James Purser
2005-04-21 1:38 ` Patrick McFarland
2005-04-21 2:01 ` Alejandro Bonilla
2005-04-21 4:03 ` Barry K. Nathan
2005-04-21 8:17 ` Martin Schlemmer
2005-04-21 8:49 ` Jan Dittmer
2005-04-21 8:59 ` Jan Dittmer
2005-04-21 9:10 ` Geert Uytterhoeven
2005-04-21 16:11 ` Al Viro
2005-04-21 17:39 ` Al Viro
2005-04-22 22:18 ` Roman Zippel
2005-05-30 23:48 ` more thread_info patches Roman Zippel
2005-05-30 23:50 ` Roman Zippel
2005-05-30 23:51 ` Roman Zippel
2005-05-31 12:16 ` Vincent Hanquez
2005-05-30 23:52 ` Roman Zippel
2005-05-31 1:25 ` randy_dunlap
2005-05-31 9:35 ` Roman Zippel
2005-05-31 15:37 ` randy_dunlap [this message]
2005-04-21 17:45 ` Linux 2.6.12-rc3 Al Viro
2005-04-21 17:57 ` Al Viro
2005-04-21 18:08 ` Al Viro
2005-04-25 19:14 ` Geert Uytterhoeven
2005-04-26 3:24 ` Al Viro
2005-04-26 8:21 ` Geert Uytterhoeven
2005-04-21 18:04 ` Al Viro
2005-04-25 19:12 ` Geert Uytterhoeven
2005-04-21 11:20 ` Pavel Machek
2005-04-21 12:03 ` Pavel Machek
2005-04-21 16:22 ` Petr Baudis
2005-04-21 19:00 ` Pavel Machek
2005-04-21 19:09 ` Petr Baudis
2005-04-21 21:38 ` Pavel Machek
2005-04-21 21:41 ` Petr Baudis
2005-04-23 21:31 ` Pavel Machek
2005-04-21 23:22 ` Pavel Machek
2005-04-21 23:33 ` Linus Torvalds
2005-04-22 0:21 ` Petr Baudis
2005-04-22 23:18 ` Pavel Machek
2005-04-23 0:21 ` Linus Torvalds
2005-04-23 11:19 ` Pavel Machek
2005-04-23 14:15 ` Linus Torvalds
2005-04-23 16:27 ` Pierre Ossman
2005-04-23 22:02 ` Greg KH
2005-04-23 22:29 ` Pavel Machek
2005-04-23 23:38 ` Greg KH
2005-04-24 10:26 ` Andrew Morton
2005-04-24 17:44 ` Linus Torvalds
2005-04-24 19:06 ` Sam Ravnborg
2005-04-24 19:55 ` Greg KH
2005-04-24 20:17 ` Pavel Machek
2005-04-24 20:29 ` Pavel Machek
2005-04-24 22:48 ` David S. Miller
2005-04-24 23:17 ` Marcel Holtmann
2005-04-25 7:40 ` Anton Altaparmakov
2005-04-26 5:25 ` Len Brown
2005-04-26 5:50 ` Andrew Morton
2005-04-23 23:00 ` Pavel Machek
2005-04-23 23:06 ` Petr Baudis
2005-04-24 7:21 ` Pavel Machek
2005-04-24 7:35 ` Dmitry Torokhov
2005-04-24 5:45 ` Greg KH
2005-04-23 12:21 ` Ed Tomlinson
2005-04-23 23:23 ` Petr Baudis
2005-04-24 7:25 ` Pavel Machek
2005-04-21 12:18 ` Martin Schlemmer
2005-04-22 7:55 ` H. Peter Anvin
2005-04-21 12:19 ` Ralf Hildebrandt
2005-04-21 15:45 ` Randy.Dunlap
2005-04-21 13:33 ` Andreas Steinmetz
2005-04-22 0:31 ` Greg KH
2005-04-21 14:24 ` Linux 2.6.12-rc3: Oops on IDE flash disk eject Andreas Steinmetz
2005-04-21 15:27 ` Andreas Steinmetz
2005-04-21 17:00 ` Linux 2.6.12-rc3: various swsusp problems Andreas Steinmetz
2005-04-21 18:57 ` Pavel Machek
2005-04-21 20:02 ` Andreas Steinmetz
2005-04-25 9:50 ` Pavel Machek
2005-04-21 20:55 ` Andreas Steinmetz
2005-04-22 15:13 ` Stefan Seyfried
2005-04-23 2:57 ` Dmitry Torokhov
2005-04-23 8:18 ` Stefan Seyfried
2005-04-23 9:14 ` Pavel Machek
2005-04-21 19:10 ` Linux 2.6.12-rc3 Benoit Boissinot
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=20050531083759.320ccb5a.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=geert@linux-m68k.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@vger.kernel.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zippel@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).