From: John Levon <levon@movementarian.org>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: "David S. Miller" <davem@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] [8/7] oprofile - dcookies need to use u32
Date: Wed, 16 Oct 2002 02:35:40 +0100 [thread overview]
Message-ID: <20021016013540.GA48543@compsoc.man.ac.uk> (raw)
In-Reply-To: <Pine.LNX.4.44.0210151830550.1203-100000@home.transmeta.com>
On Tue, Oct 15, 2002 at 06:33:51PM -0700, Linus Torvalds wrote:
> Ok, everything applied.
Thanks !
> Quite frankly, as long as the vtune user-level tools are all proprietary,
> I don't really care all that much about vtune compatibility, but if it
> turns out to be easy and convenient we might as well try to be polite
> about it (and apparently they've sorted out all the issues with their
> kernel-level code, and are happy to do that stuff all GPL'd, but since
> it's pretty useless without the tools..).
>From my discussions with the vtune people, their kernel-level stuff has
almost exactly the same needs as oprofile. So I think they have
everything they need already (and I had to go to the effort of a total
rewrite, I think they should as well ...)
In fact I don't see a reason why they couldn't just use the oprofile
code directly anyway, and just have the propietary goop read from
/dev/oprofile/buffer. Especially if that encourages them to port the
PEBS support etc.
regards
john
--
"It's a cardboard universe ... and if you lean too hard against it, you fall
through."
- Philip K. Dick
next prev parent reply other threads:[~2002-10-16 1:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-15 22:32 [PATCH] [2/7] oprofile - dcookies John Levon
2002-10-15 23:37 ` David S. Miller
2002-10-15 23:47 ` John Levon
2002-10-16 0:06 ` [PATCH] [8/7] oprofile - dcookies need to use u32 John Levon
2002-10-16 0:01 ` David S. Miller
2002-10-16 1:33 ` Linus Torvalds
2002-10-16 1:35 ` John Levon [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-10-16 1:56 Ulrich Weigand
2002-10-16 2:00 ` David S. Miller
2002-10-16 16:40 ` John Levon
2002-10-16 18:29 ` Jeff Garzik
2002-10-16 21:38 ` David S. Miller
2002-10-17 0:57 ` John Levon
2002-10-17 0:55 ` David S. Miller
2002-10-17 1:16 ` John Levon
2002-10-17 1:12 ` David S. Miller
2002-10-19 0:26 ` John Levon
2002-10-19 0:23 ` David S. Miller
2002-10-19 0:34 ` John Levon
2002-10-19 0:31 ` David S. Miller
2002-10-19 0:40 ` John Levon
2002-10-19 0:35 ` David S. Miller
2002-11-01 4:33 ` John Levon
2002-11-01 10:27 ` David S. Miller
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=20021016013540.GA48543@compsoc.man.ac.uk \
--to=levon@movementarian.org \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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