From: Ingo Molnar <mingo@elte.hu>
To: Stefani Seibold <stefani@seibold.net>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
"H. Peter Anvin" <hpa@zytor.com>,
Americo Wang <xiyou.wangcong@gmail.com>,
Thomas Gleixner <tglx@linutronix.de>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: [PATCH] RFC x86_64 more accurate KSTK_ESP implementation
Date: Sun, 8 Nov 2009 13:55:27 +0100 [thread overview]
Message-ID: <20091108125527.GA19350@elte.hu> (raw)
In-Reply-To: <1257684666.20579.9.camel@wall-e>
* Stefani Seibold <stefani@seibold.net> wrote:
> > I'd suggest a competely different method: why dont you use an IPI to
> > sample the SP whenever someone wants to read it from /proc and we
> > see that the task is running on a CPU right now?
>
> Sounds like a challenge, i like the idea. I will have a look on it...
It's not a fastpath, so smp_function_call() ought to do the trick.
Ingo
next prev parent reply other threads:[~2009-11-08 12:55 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 [this message]
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
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=20091108125527.GA19350@elte.hu \
--to=mingo@elte.hu \
--cc=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stefani@seibold.net \
--cc=tglx@linutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.