linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 30 May 2005 18:25:11 -0700	[thread overview]
Message-ID: <20050530182511.434b0e97.rdunlap@xenotime.net> (raw)
In-Reply-To: <Pine.LNX.4.61.0505310113370.10977@scrub.home>

On Tue, 31 May 2005 01:48:28 +0200 (CEST) Roman Zippel wrote:

| Hi,
| 
| On Thu, 21 Apr 2005, Al Viro wrote:
| 
| > 	thread_info, part 1:
| 
| Here are some possible followup patches. Since it's already some time ago 
| here are the original posts for everyone else:
| http://marc.theaimsgroup.com/?l=linux-kernel&m=111410539627881&w=2
| 
| This introduces an additional stack variable in task_struct. It's 
| basically redundant with the thread_info pointer, but in the long term I'd 
| like to get of the latter (with the following patches).
| 
| ---
| 
|  include/linux/init_task.h |    1 +
|  include/linux/sched.h     |    1 +
|  kernel/fork.c             |    1 +
|  3 files changed, 3 insertions(+)
| 
| 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?


And a general comments about the 4 emails:
they all have the same subject.  :(

I guess you need to read & follow:
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
and
http://linux.yyz.us/patch-format.html

so that Andrew doesn't have to keep saying this over and over again
(no, it's not just you).


|  	atomic_t usage;
|  	unsigned long flags;	/* per process flags, defined below */
|  	unsigned long ptrace;
| Index: linux-2.6-mm/include/linux/init_task.h
| ===================================================================
| --- linux-2.6-mm.orig/include/linux/init_task.h	2005-05-31 01:19:01.636591190 +0200
| +++ linux-2.6-mm/include/linux/init_task.h	2005-05-31 01:19:05.913856451 +0200
| @@ -71,6 +71,7 @@ extern struct group_info init_groups;
|  {									\
|  	.state		= 0,						\
|  	.thread_info	= &init_thread_info,				\
| +	.stack		= &init_stack,					\
|  	.usage		= ATOMIC_INIT(2),				\
|  	.flags		= 0,						\
|  	.lock_depth	= -1,						\
| Index: linux-2.6-mm/kernel/fork.c
| ===================================================================
| --- linux-2.6-mm.orig/kernel/fork.c	2005-05-31 01:19:01.636591190 +0200
| +++ linux-2.6-mm/kernel/fork.c	2005-05-31 01:19:29.954726757 +0200
| @@ -173,6 +173,7 @@ static struct task_struct *dup_task_stru
|  	*tsk = *orig;
|  	setup_thread_info(tsk, ti);
|  	tsk->thread_info = ti;
| +	tsk->stack = ti;
|  	ti->task = tsk;
|  
|  	/* One for us, one for whoever does the "release_task()" (usually parent) */
| -

---
~Randy

  parent reply	other threads:[~2005-05-31  1:26 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 [this message]
2005-05-31  9:35             ` Roman Zippel
2005-05-31 15:37               ` randy_dunlap
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=20050530182511.434b0e97.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).