mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@user.it.uu.se>
To: Hiro Yoshioka <hyoshiok@miraclelinux.com>
Cc: perfctr-devel@lists.sourceforge.net,
	linux-kernel@vger.kernel.org,
	hardmeter-users@lists.sourceforge.jp
Subject: Re: [Perfctr-devel] perfctr and Linus' tree?
Date: Fri, 7 Mar 2003 14:30:16 +0100	[thread overview]
Message-ID: <15976.40680.424597.305633@gargle.gargle.HOWL> (raw)
In-Reply-To: <20030307153354J.hyoshiok@miraclelinux.com>

Hiro Yoshioka writes:
 > I have a question. Is there any progress on merging the
 > perfctr patch to Linus' kernel tree?
 > 
 > http://www.uwsg.iu.edu/hypermail/linux/kernel/0303.0/0647.html
 > 
 > I found the DCL patch set includes the perfctr patch.
 > http://lists.osdl.org/pipermail/dcl_developer/2003-March/000009.html

No progress since Linus totally ignored it, but at least two
perfctr-patched trees exist. OSDL does one for the development
kernel, and Jack Perdue has pre-patched RedHat kernel .rpms.
(For Jack's stuff, check out PAPI -> Links -> Related Software.)

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.)

/Mikael

  reply	other threads:[~2003-03-07 13:20 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-07  6:33 Hiro Yoshioka
2003-03-07 13:30 ` Mikael Pettersson [this message]
2003-03-10  7:43   ` [Perfctr-devel] " Hiro Yoshioka
2003-03-07 20:14 Albert Cahalan
2003-03-08  1:02 Mikael Pettersson

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=15976.40680.424597.305633@gargle.gargle.HOWL \
    --to=mikpe@user.it.uu.se \
    --cc=hardmeter-users@lists.sourceforge.jp \
    --cc=hyoshiok@miraclelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perfctr-devel@lists.sourceforge.net \
    /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

all inboxes | Powered by JetHome®