From: Masami Hiramatsu <masami.hiramatsu.pt@hitachi.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Srikar Dronamraju <srikar@linux.vnet.ibm.com>,
Ingo Molnar <mingo@elte.hu>,
Linus Torvalds <torvalds@linux-foundation.org>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>,
LKML <linux-kernel@vger.kernel.org>,
Oleg Nesterov <oleg@redhat.com>,
Christoph Hellwig <hch@infradead.org>,
Arnaldo Carvalho de Melo <acme@infradead.org>,
Anton Arapov <anton@redhat.com>,
Stephen Boyd <sboyd@codeaurora.org>,
yrl.pp-manager.tt@hitachi.com
Subject: Re: Re: [PATCH v20] tracing: Fix kconfig warning due to a typo
Date: Thu, 10 May 2012 20:47:53 +0900 [thread overview]
Message-ID: <4FABAAE9.6040701@hitachi.com> (raw)
In-Reply-To: <1336561050.2527.14.camel@twins>
(2012/05/09 19:57), Peter Zijlstra wrote:
> On Wed, 2012-05-09 at 14:55 +0900, Masami Hiramatsu wrote:
>> Would you mean SIB + displacement addressing? :)
>
> Yeah something like that. Basically something that's powerful enough to
> cover all things directly addressable by an architecture (for all
> archs). So that if you put a probe at a specific location you can indeed
> obtain all life variables at that spot.
>
> This would include segment prefixes for x86 so we can get at per-cpu
> variables.
Ah, right. Hmm, the problem is that this interface's syntax should be
arch-independent. It need to be extended to support more complex
addressing mode.
Thank you for the request!
--
Masami HIRAMATSU
Software Platform Research Dept. Linux Technology Center
Hitachi, Ltd., Yokohama Research Laboratory
E-mail: masami.hiramatsu.pt@hitachi.com
next prev parent reply other threads:[~2012-05-10 11:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-08 11:11 [PATCH v20] tracing: Fix kconfig warning due to a typo Srikar Dronamraju
2012-05-08 11:29 ` Peter Zijlstra
2012-05-08 12:48 ` Steven Rostedt
2012-05-08 13:17 ` Peter Zijlstra
2012-05-09 5:55 ` Masami Hiramatsu
2012-05-09 10:57 ` Peter Zijlstra
2012-05-10 11:47 ` Masami Hiramatsu [this message]
2012-05-08 12:49 ` [tip:perf/uprobes] " tip-bot for Srikar Dronamraju
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=4FABAAE9.6040701@hitachi.com \
--to=masami.hiramatsu.pt@hitachi.com \
--cc=acme@infradead.org \
--cc=ananth@in.ibm.com \
--cc=anton@redhat.com \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sboyd@codeaurora.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=torvalds@linux-foundation.org \
--cc=yrl.pp-manager.tt@hitachi.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.