[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20081205.002701.172921476.davem@davemloft.net>
Date: Fri, 05 Dec 2008 00:27:01 -0800 (PST)
From: David Miller <davem@...emloft.net>
To: mingo@...e.hu
Cc: a.p.zijlstra@...llo.nl, paulus@...ba.org, tglx@...utronix.de,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
akpm@...ux-foundation.org, eranian@...glemail.com,
dada1@...mosbay.com, robert.richter@....com, arjan@...radead.org,
hpa@...or.com, rostedt@...dmis.org
Subject: Re: [patch 0/3] [Announcement] Performance Counters for Linux
From: Ingo Molnar <mingo@...e.hu>
Date: Fri, 5 Dec 2008 09:24:31 +0100
> Right now we begun with the most trivial ones:
>
> enum perf_record_type {
> PERF_RECORD_SIMPLE,
> PERF_RECORD_IRQ,
> };
>
> ... but it would be natural to do a PERF_RECORD_GP_REGISTERS as well.
> Perhaps even a PERF_RECORD_STACKTRACE using the sysprof facilities, to do
> a hierarchic multi-dimension profile that sysprof does so nicely.
Maybe even add something like PERF_RECORD_THE_MOON...
see how rediculious this is?
It's not your business in the kernel to decide what things are
useful. The monitor can stop the task and inspect whatever
it wants with _existing_ facilities. We need none of this stuff.
--
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/
Powered by blists - more mailing lists