linux-kernel - Re: [tip:perfcounters/core] perf record/report: Add call graph / call chain profiling

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] [day] [month] [year] [list]

Date:	Wed, 17 Jun 2009 14:24:55 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc:	Frederic Weisbecker <fweisbec@...il.com>, mingo@...hat.com,
	hpa@...or.com, paulus@...ba.org, acme@...hat.com,
	linux-kernel@...r.kernel.org, penberg@...helsinki.fi,
	efault@....de, arjan@...radead.org, tglx@...utronix.de,
	linux-tip-commits@...r.kernel.org,
	Corey Ashford <cjashfor@...ux.vnet.ibm.com>
Subject: Re: [tip:perfcounters/core] perf record/report: Add call graph /
	call chain profiling


* Peter Zijlstra <a.p.zijlstra@...llo.nl> wrote:

> > The context IDs would occupy some rare and 
> > unlikely-to-be-allocated-soon corner of the address space - say 
> > startig at 0x8765432112345000. (and real RIPs would be filtered 
> > and nudged just outside that space of a handful IDs.)
> 
> Right, that works too, but should we use (u64)-1..-4095 for that? 
> We already use that range for things like ERR_PTR() so its very 
> unlikely we have something sensible mapped there.

Makes sense. It's also an easier (and more natural) enumeration 
method.

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