From: William Lee Irwin III <wli@holomorphy.com>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.8-rc3-mm1
Date: Thu, 5 Aug 2004 05:50:18 -0700 [thread overview]
Message-ID: <20040805125018.GB14358@holomorphy.com> (raw)
In-Reply-To: <20040805031918.08790a82.akpm@osdl.org>
On Thu, Aug 05, 2004 at 03:19:18AM -0700, Andrew Morton wrote:
> +consolidate-prof_cpu_mask.patch
> +profile_pc.patch
> +profile_tick.patch
> +profile-tick-fix.patch
> +move-profile-operations.patch
> +make-private-profile-state-static.patch
> +make-prof_buffer-atomic_t.patch
> Consolidate a lot of the kernel profiling code.
Minor gaffe on my part:
--- mm1-2.6.8-rc3/include/asm-ia64/ptrace.h.orig 2004-08-05 22:42:16.312957563 -0700
+++ mm1-2.6.8-rc3/include/asm-ia64/ptrace.h 2004-08-05 22:46:36.284634066 -0700
@@ -232,11 +232,11 @@
/* Conserve space in histogram by encoding slot bits in address
* bits 2 and 3 rather than bits 0 and 1.
*/
-static inline unsigned long profile_pc(struct pt_regs *regs)
-{
- unsigned long ip = instruction_pointer(regs);
- return (ip & ~3UL) + ((ip & 3UL) << 2);
-}
+#define profile_pc(regs) \
+({ \
+ unsigned long __ip = instruction_pointer(regs); \
+ (__ip & ~3UL) + ((__ip & 3UL) << 2); \
+})
/* given a pointer to a task_struct, return the user's pt_regs */
# define ia64_task_regs(t) (((struct pt_regs *) ((char *) (t) + IA64_STK_OFFSET)) - 1)
next prev parent reply other threads:[~2004-08-05 12:57 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-05 10:19 2.6.8-rc3-mm1 Andrew Morton
2004-08-05 11:18 ` 2.6.8-rc3-mm1: SCHEDSTATS compile error Adrian Bunk
2004-08-05 15:25 ` Martin J. Bligh
2004-08-05 16:49 ` Adrian Bunk
2004-08-05 18:17 ` Rick Lindsley
2004-08-05 18:20 ` Adrian Bunk
2004-08-05 19:15 ` Rick Lindsley
2004-08-05 19:54 ` Luiz Fernando N. Capitulino
2004-08-05 20:20 ` Adrian Bunk
2004-08-09 19:46 ` Bill Davidsen
2004-08-09 19:51 ` Rick Lindsley
2004-08-05 11:20 ` 2.6.8-rc3-mm1 Sean Neakums
2004-08-05 11:49 ` 2.6.8-rc3-mm1: ALSA: vortex_asXtalkGainsAllChan multiple definitions Adrian Bunk
2004-08-05 12:38 ` 2.6.8-rc3-mm1: ip2mainc-add-missing-pci_enable_device breaks compilation Adrian Bunk
2004-08-05 15:45 ` Bjorn Helgaas
2004-08-05 12:50 ` William Lee Irwin III [this message]
2004-08-05 13:03 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 21:38 ` 2.6.8-rc3-mm1 Andrew Morton
2004-08-06 15:25 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 13:24 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 13:36 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 16:13 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-05 16:42 ` 2.6.8-rc3-mm1 Christoph Hellwig
2004-08-05 20:24 ` 2.6.8-rc3-mm1 Alan Cox
2004-08-05 16:52 ` 2.6.8-rc3-mm1 (compile stats) John Cherry
2004-08-06 3:34 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06 4:24 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06 4:39 ` 2.6.8-rc3-mm1 William Lee Irwin III
2004-08-06 5:17 ` 2.6.8-rc3-mm1 Andrew Morton
[not found] ` <20040806075219.GW17188@holomorphy.com>
2004-08-06 8:11 ` alpha signal race fixes William Lee Irwin III
2004-08-06 12:48 ` 2.6.8-rc3-mm1 Mark Watts
2004-08-06 19:58 ` 2.6.8-rc3-mm1: sk98lin/skge.c compile error with PROC_FS=n Adrian Bunk
2004-08-06 19:58 ` 2.6.8-rc3-mm1: PROC_FS=n link errors Adrian Bunk
2004-08-06 20:24 ` William Lee Irwin III
2004-08-06 20:33 ` William Lee Irwin III
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=20040805125018.GB14358@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--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