linux-kernel - Re: [PATCH] tracing/function-branch-tracer: support for x86-64

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c62985530812021340n47999897yfe1359792b96c8e3@mail.gmail.com>
Date:	Tue, 2 Dec 2008 22:40:09 +0100
From:	"Frédéric Weisbecker" <fweisbec@...il.com>
To:	"Steven Rostedt" <rostedt@...dmis.org>
Cc:	"Ingo Molnar" <mingo@...e.hu>, "Tim Bird" <tim.bird@...sony.com>,
	"Linux Kernel" <linux-kernel@...r.kernel.org>,
	"Alexander van Heukelum" <heukelum@...lshack.com>
Subject: Re: [PATCH] tracing/function-branch-tracer: support for x86-64

2008/12/2 Steven Rostedt <rostedt@...dmis.org>:
> Hmm, I had issues with my mail server so I just received this. I was
> porting it to x86-64 last night too.

Oops...


> I'm also working on a way to trigger
> specific functions to trace instead of tracing all functions.

You mean only tracing one function and its tree of calls (by defining
a kind of root
of tracing?) as suggested Arjan?
Yeah, that would be great.

To define it through trace_filter, perhaps we could use the sign "^"
before a function name to say:
"all calls which starts with this function". I hope that wouldn't
confuse with the real sense that "^" has in regular
expressions.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/