Re: [tip:perfcounters/core] perf record/report: Add call graph / call chain profiling
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [tip:perfcounters/core] perf record/report: Add call graph / call chain profiling
- From: Ingo Molnar <mingo@xxxxxxx>
- Date: Wed, 17 Jun 2009 14:24:55 +0200
- Cc: Frederic Weisbecker <fweisbec@xxxxxxxxx>, mingo@xxxxxxxxxx, hpa@xxxxxxxxx, paulus@xxxxxxxxx, acme@xxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx, penberg@xxxxxxxxxxxxxx, efault@xxxxxx, arjan@xxxxxxxxxxxxx, tglx@xxxxxxxxxxxxx, linux-tip-commits@xxxxxxxxxxxxxxx, Corey Ashford <cjashfor@xxxxxxxxxxxxxxxxxx>
- In-reply-to: <1245224279.13761.21585.camel@twins>
- References: <tip-3efa1cc99ec51bc7a7ae0011a16619fd20dbe6ea@xxxxxxxxxxxxxx> <20090616025750.GB6057@nowhere> <20090616080924.GB16229@xxxxxxx> <1245224279.13761.21585.camel@twins>
- User-agent: Mutt/1.5.18 (2008-05-17)
* Peter Zijlstra <a.p.zijlstra@xxxxxxxxx> 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-tip-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
[Index of Archives]
[Linux Stable Commits]
[Linux Stable Kernel]
[Linux Kernel]
[Linux USB Devel]
[Linux Video &Media]
[Linux Audio Users]
[Yosemite News]
[Linux SCSI]