From: Andrew Morton <akpm@osdl.org>
To: jbarnes@sgi.com (Jesse Barnes)
Cc: juan.villacis@intel.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.x] additional kernel event notifications
Date: Fri, 19 Sep 2003 11:28:09 -0700 [thread overview]
Message-ID: <20030919112809.21fe773b.akpm@osdl.org> (raw)
In-Reply-To: <20030919181822.GA4335@sgi.com>
jbarnes@sgi.com (Jesse Barnes) wrote:
>
> Any chance of this getting into 2.6? I for one would like to see it so
> that the performance monitoring tools can work properly without having
> to resort to syscall table patching.
If the code which uses these hooks is included in the kernel.org tree, yes.
If the code which needs the hooks is not in the kernel.org tree then people
can patch the core kernel at the same time as adding the performance
analysis patch.
If the code which needs these hooks is not appropriately licensed then
these hooks basically constitute a GPL bypass and that is not a direction
we wish to be heading in.
next prev parent reply other threads:[~2003-09-19 18:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-18 6:20 [PATCH 2.6.x] additional kernel event notifications Villacis, Juan
2003-09-19 18:18 ` Jesse Barnes
2003-09-19 18:28 ` Andrew Morton [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-19 19:32 Villacis, Juan
2003-09-19 19:35 ` Andrew Morton
2003-09-19 20:00 Nakajima, Jun
2003-09-19 21:18 Villacis, Juan
2003-09-19 21:28 ` Andrew Morton
2003-09-20 17:24 ` Anton Blanchard
2003-09-20 0:57 Villacis, Juan
2003-09-20 2:23 ` John Levon
[not found] <xAZi.1DR.1@gated-at.bofh.it>
2003-09-20 2:02 ` Andi Kleen
2003-09-22 5:59 Villacis, Juan
2003-09-22 11:07 ` John Levon
2003-09-22 6:23 Villacis, Juan
2003-09-23 1:16 Villacis, Juan
2003-09-23 10:16 ` John Levon
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=20030919112809.21fe773b.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=jbarnes@sgi.com \
--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