From: Andi Kleen <ak@muc.de>
To: "Villacis, Juan" <juan.villacis@intel.com>
Cc: akpm@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.x] additional kernel event notifications
Date: Sat, 20 Sep 2003 04:02:08 +0200 [thread overview]
Message-ID: <m3llskz07z.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <xAZi.1DR.1@gated-at.bofh.it> ("Villacis, Juan"'s message of "Fri, 19 Sep 2003 23:30:09 +0200")
"Villacis, Juan" <juan.villacis@intel.com> writes:
> The current event notifications used by tools like Oprofile, while quite
> useful, are not sufficient. The additional event notifications we
> propose can provide a more complete picture for performance tuning on
> Linux, particularly for dynamically generated code (such as found in
> Java).
Can you explain why profiling dynamically generated code needs kernel
support? The kernel should not know anything about this.
The original oprofile patch also added similar hooks, but they were
not merged. Instead the "dcookies" mechanism was added to assign samples to
specific executables. Why can't you use the same mechanism?
There is not more information in the kernel than what dcookies
already provide.
-Andi
next parent reply other threads:[~2003-09-20 2:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xAZi.1DR.1@gated-at.bofh.it>
2003-09-20 2:02 ` Andi Kleen [this message]
2003-09-23 1:16 [PATCH 2.6.x] additional kernel event notifications Villacis, Juan
2003-09-23 10:16 ` John Levon
-- strict thread matches above, loose matches on Subject: below --
2003-09-22 6:23 Villacis, Juan
2003-09-22 5:59 Villacis, Juan
2003-09-22 11:07 ` John Levon
2003-09-20 0:57 Villacis, Juan
2003-09-20 2:23 ` John Levon
2003-09-19 21:18 Villacis, Juan
2003-09-19 21:28 ` Andrew Morton
2003-09-20 17:24 ` Anton Blanchard
2003-09-19 20:00 Nakajima, Jun
2003-09-19 19:32 Villacis, Juan
2003-09-19 19:35 ` Andrew Morton
2003-09-18 6:20 Villacis, Juan
2003-09-19 18:18 ` Jesse Barnes
2003-09-19 18:28 ` Andrew Morton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3llskz07z.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=akpm@osdl.org \
--cc=juan.villacis@intel.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox