linux-kernel - Re: [PATCH 03/23] perf: Add ability to attach user level registers dump to sample

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: <20120629113012.GF6978@krava.brq.redhat.com>
Date:	Fri, 29 Jun 2012 13:30:12 +0200
From:	Jiri Olsa <jolsa@...hat.com>
To:	Frederic Weisbecker <fweisbec@...il.com>
Cc:	Peter Zijlstra <a.p.zijlstra@...llo.nl>,
	Stephane Eranian <eranian@...gle.com>, acme@...hat.com,
	mingo@...e.hu, paulus@...ba.org, cjashfor@...ux.vnet.ibm.com,
	gorcunov@...nvz.org, tzanussi@...il.com, mhiramat@...hat.com,
	robert.richter@....com, fche@...hat.com,
	linux-kernel@...r.kernel.org, masami.hiramatsu.pt@...achi.com,
	drepper@...il.com, asharma@...com, benjamin.redelings@...cent.org,
	"H. Peter Anvin" <hpa@...ux.intel.com>
Subject: Re: [PATCH 03/23] perf: Add ability to attach user level registers
 dump to sample

On Fri, Jun 29, 2012 at 01:23:51PM +0200, Frederic Weisbecker wrote:

SNIP

> > 
> > well, thats basically what we have now..
> > 
> > when the kernel is compiled for 32 bits, the bitmask allows to store:
> > 
> > ax, bx, cx, dx, si, di, bp, sp, ip, flags, cs, ds, es, fs, gs, ss
> > 
> > and when  kernel is compiled for 64 bits, the bitmask adds 64bit stuff:
> > 
> > ax, bx, cx, dx, si, di, bp, sp, ip, flags, cs, ds, es, fs, gs, ss
> > r8, r9, r10, r11, r12, r13, r14, r15
> > 
> > 
> > - 32 bits kernel is straightforward
> > 
> > - for 64 bits kernel we store whatever bitmask instructs to,
> >   regardless if we are in compat task or native 64,
> >   user space will deal with that in post processing
> 
> I can think of the crazy scenario where perf itself is compat and there
> are 64 bits apps that will be profiled by perf. It means perf must check
> if the kernel is 32 or 64 and depending on this, request r8-r15 or not.
> 
> May be that's just too unlikely to matter.

hopefully ;) anyway the kernel interface stays the same in this case as well

we can add this check later when/if we deal with compat tasks

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