From: Stefani Seibold <stefani@seibold.net>
To: Andi Kleen <andi@firstfloor.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Americo Wang <xiyou.wangcong@gmail.com>
Subject: Re: [PATCH] update fix X86_64 procfs provide stack information for threads
Date: Wed, 04 Nov 2009 23:21:15 +0100 [thread overview]
Message-ID: <1257373275.18448.7.camel@wall-e> (raw)
In-Reply-To: <20091104120019.GK31511@one.firstfloor.org>
Hi Andi,
what do you think about this? The following patch implements a more
accurate KSTK_ESP. The usersp of the task will be updated in the device
and apci_timer interrupt. It would be easy to change other interrupts
too. The performance penalty should tiny.
--- linux-2.6.32-rc5.old/arch/x86/include/asm/processor.h 2009-10-16 02:41:50.000000000 +0200
+++ linux-2.6.32-rc5.new/arch/x86/include/asm/processor.h 2009-11-04 23:02:53.705275836 +0100
@@ -1000,7 +1000,7 @@
#define thread_saved_pc(t) (*(unsigned long *)((t)->thread.sp - 8))
#define task_pt_regs(tsk) ((struct pt_regs *)(tsk)->thread.sp0 - 1)
-#define KSTK_ESP(tsk) -1 /* sorry. doesn't work for syscall. */
+extern unsigned long KSTK_ESP(struct task_struct *task);
#endif /* CONFIG_X86_64 */
extern void start_thread(struct pt_regs *regs, unsigned long new_ip,
@@ -1052,4 +1052,12 @@
return ratio;
}
+#define update_usersp(regs) \
+({ \
+ unsigned long __stk__ = (unsigned long)task_stack_page(current); \
+ unsigned long __stkp__ = (regs)->sp; \
+ if ((__stkp__ < __stk__) || (__stkp__ >= __stk__ + THREAD_SIZE)) \
+ current->thread.usersp = __stkp__; \
+})
+
#endif /* _ASM_X86_PROCESSOR_H */
--- x/linux-2.6.32-rc5/arch/x86/kernel/process_64.c 2009-10-16 02:41:50.000000000 +0200
+++ linux-2.6.32-rc5/arch/x86/kernel/process_64.c 2009-11-03 10:11:11.202957393 +0100
@@ -664,3 +664,9 @@
return do_arch_prctl(current, code, addr);
}
+unsigned long KSTK_ESP(struct task_struct *task)
+{
+ return (test_tsk_thread_flag(task, TIF_IA32)) ? \
+ (task_pt_regs(task)->sp) : \
+ ((task)->thread.usersp);
+}
--- linux-2.6.32-rc5.old/arch/x86/kernel/irq_64.c 2009-10-16 02:41:50.000000000 +0200
+++ linux-2.6.32-rc5.new/arch/x86/kernel/irq_64.c 2009-11-04 22:29:55.762951577 +0100
@@ -53,6 +53,7 @@
struct irq_desc *desc;
stack_overflow_check(regs);
+ update_usersp(regs);
desc = irq_to_desc(irq);
if (unlikely(!desc))
--- linux-2.6.32-rc5.old/arch/x86/kernel/apic/apic.c 2009-10-16 02:41:50.000000000 +0200
+++ linux-2.6.32-rc5.new/arch/x86/kernel/apic/apic.c 2009-11-04 23:12:32.805086991 +0100
@@ -831,6 +831,9 @@
{
struct pt_regs *old_regs = set_irq_regs(regs);
+#ifndef CONFIG_X86_32
+ update_usersp(regs);
+#endif
/*
* NOTE! We'd better ACK the irq immediately,
* because timer handling can be slow.
This works in my environment under load, but i have not the oversight if it work
under all circumstances.
Stefani
prev parent reply other threads:[~2009-11-04 22:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 7:31 [PATCH] update fix X86_64 procfs provide stack information for threads Stefani Seibold
2009-11-03 8:28 ` Ingo Molnar
2009-11-03 9:06 ` Stefani Seibold
2009-11-03 18:16 ` Ingo Molnar
2009-11-05 8:19 ` [PATCH] RFC x86_64 more accurate KSTK_ESP implementation Stefani Seibold
2009-11-05 11:08 ` Andi Kleen
2009-11-05 12:11 ` Stefani Seibold
2009-11-08 11:35 ` Ingo Molnar
2009-11-08 12:51 ` Stefani Seibold
2009-11-08 12:55 ` Ingo Molnar
2009-11-08 14:00 ` Stefani Seibold
2009-11-08 16:34 ` H. Peter Anvin
2009-11-08 19:37 ` Andi Kleen
2009-11-05 13:02 ` [PATCH] fix /proc/<pid>/stat stack pointer for kernel threads Stefani Seibold
2009-11-13 8:01 ` [tip:x86/urgent] fs: " Stefani Seibold
2009-11-04 11:17 ` [PATCH] update fix X86_64 procfs provide stack information for threads Andi Kleen
2009-11-04 11:50 ` Stefani Seibold
2009-11-04 12:00 ` Andi Kleen
2009-11-04 12:22 ` Stefani Seibold
2009-11-04 15:42 ` Stefani Seibold
2009-11-04 22:21 ` Stefani Seibold [this message]
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=1257373275.18448.7.camel@wall-e \
--to=stefani@seibold.net \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=xiyou.wangcong@gmail.com \
/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