linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test11-wli-1
Date: Mon, 8 Dec 2003 05:57:37 -0800	[thread overview]
Message-ID: <20031208135737.GG8039@holomorphy.com> (raw)
In-Reply-To: <20031204200120.GL19856@holomorphy.com>

On Thu, Dec 04, 2003 at 12:01:20PM -0800, William Lee Irwin III wrote:
> Successfully tested on a Thinkpad T21. Any feedback regarding
> performance would be very helpful. Desktop users should notice top(1)
> is faster, kernel hackers that kernel compiles are faster, and highmem
> users should see much less per-process lowmem overhead.

Woops, I missed the target by a few bytes. Probably a bit overwrought:


-- wli


diff -prauN wli-2.6.0-test11-36/include/asm-i386/processor.h wli-2.6.0-test11-37/include/asm-i386/processor.h
--- wli-2.6.0-test11-36/include/asm-i386/processor.h	2003-12-03 19:40:24.000000000 -0800
+++ wli-2.6.0-test11-37/include/asm-i386/processor.h	2003-12-07 06:36:51.000000000 -0800
@@ -497,11 +497,19 @@ void show_trace(struct task_struct *task
 unsigned long get_wchan(struct task_struct *task);
 
 #define THREAD_SIZE_LONGS	(THREAD_SIZE/sizeof(unsigned long))
+#define KSTK_TOP(info)							\
+({									\
+	unsigned long *__ptr = (unsigned long *)(info);			\
+	(unsigned long)(&__ptr[THREAD_SIZE_LONGS]);			\
+})
+
 #define task_pt_regs(task)						\
 ({									\
-	unsigned long *__ptr = (unsigned long *)(task)->thread_info;	\
-	(struct pt_regs *)(&__ptr[THREAD_SIZE_LONGS-1]);		\
+	struct pt_regs *__regs__;					\
+	__regs__ = (struct pt_regs *)KSTK_TOP((task)->thread_info);	\
+	__regs__ - 1;							\
 })
+
 #define KSTK_EIP(task)	(task_pt_regs(task)->eip)
 #define KSTK_ESP(task)	(task_pt_regs(task)->esp)
 

  parent reply	other threads:[~2003-12-08 13:57 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-04 20:01 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-04 21:01 ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-04 22:58 ` 2.6.0-test11-wli-1 Muli Ben-Yehuda
2003-12-04 23:21   ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-05  8:14 ` 2.6.0-test11-wli-1 Hugang
2003-12-05  9:10   ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-08 13:57 ` William Lee Irwin III [this message]
2003-12-08 14:03   ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-09 23:35 ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-09 23:59   ` 2.6.0-test11-wli-1 Zwane Mwaikambo
2003-12-11  1:42     ` 2.6.0-test11-wli-1 bill davidsen
2003-12-11  2:10       ` 2.6.0-test11-wli-1 William Lee Irwin III
2003-12-11  2:30         ` 2.6.0-test11-wli-1 Mike Fedyk

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=20031208135737.GG8039@holomorphy.com \
    --to=wli@holomorphy.com \
    --cc=linux-kernel@vger.kernel.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).