From: Albert Cahalan <albert@users.sf.net>
To: mikpe@user.it.uu.se
Cc: linux-kernel@vger.kernel.org
Subject: Re: [Perfctr-devel] perfctr and Linus' tree?
Date: 07 Mar 2003 15:14:15 -0500 [thread overview]
Message-ID: <1047068056.2012.72.camel@cube> (raw)
Mikael Pettersson writes:
> I'm planning to simplify the kernel <--> user-space
> interface in perfctr-2.6 (drop /proc/pid/perfctr and
> go back to /dev/perfctr), and then I _think_ I can
> do a version that doesn't require patching kernel
> source. (It will do binary code patching at module
> load-time instead. Horrible as that sounds, it's
> easier to deal with for users.)
That would make porting more difficult. I don't think
these changes will help you gain acceptance.
next reply other threads:[~2003-03-07 20:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-07 20:14 Albert Cahalan [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-03-08 1:02 [Perfctr-devel] perfctr and Linus' tree? Mikael Pettersson
2003-03-07 6:33 Hiro Yoshioka
2003-03-07 13:30 ` [Perfctr-devel] " Mikael Pettersson
2003-03-10 7:43 ` Hiro Yoshioka
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=1047068056.2012.72.camel@cube \
--to=albert@users.sf.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@user.it.uu.se \
/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