linux-kernel - Re: [RFC PATCH 2/9] perf: Add ability to dump user regs

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: <20101018223539.GB5370@nowhere>
Date:	Tue, 19 Oct 2010 00:35:42 +0200
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	LKML <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...e.hu>,
	Arnaldo Carvalho de Melo <acme@...hat.com>,
	Paul Mackerras <paulus@...ba.org>,
	Cyrill Gorcunov <gorcunov@...nvz.org>,
	Tom Zanussi <tzanussi@...il.com>,
	Masami Hiramatsu <mhiramat@...hat.com>,
	Steven Rostedt <rostedt@...dmis.org>,
	Robert Richter <robert.richter@....com>,
	David Miller <davem@...emloft.net>
Subject: Re: [RFC PATCH 2/9] perf: Add ability to dump user regs

On Mon, Oct 18, 2010 at 12:01:18PM +0200, Stephane Eranian wrote:
> On Sun, Oct 17, 2010 at 12:07 PM, Peter Zijlstra <peterz@...radead.org> wrote:
> > On Sat, 2010-10-16 at 00:58 +0200, Frederic Weisbecker wrote:
> >> > Yes, PEBS does not capture the entire state.
> >> >
> >> > Here is what you get on Intel Core:
> >> >         u64 flags, ip;
> >> >         u64 ax, bx, cx, dx;
> >> >         u64 si, di, bp, sp;
> >> >         u64 r8,  r9,  r10, r11;
> >> >         u64 r12, r13, r14, r15;
> >
> >> Ok, that seems to cover most of the state. I guess few people care
> >> about cs, ds, es, fs, gs, most of the time.
> >
> > Yeah, except if you want to profile wine or something like that ;-)
> >
> That means that if you want the segment registers, then you cannot
> use PEBS. I think you could catch that when the event is created.
> 
> The other problem here is how to name registers at the API level.
> You would be introducing architecture-specific register names
> in perf_event.h. There is no such a thing today.


That can go into an asm/perf_regs.h or something. It's up to the
arch to name its registers.

--
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/