All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hiro Yoshioka <hyoshiok@miraclelinux.com>
To: mikpe@csd.uu.se
Cc: linux-kernel@vger.kernel.org, perfctr-devel@lists.sourceforge.net
Cc: hyoshiok@miraclelinux.com, hardmeter-users@lists.sourceforge.jp
Subject: Re: [Perfctr-devel] perfctr-2.5.5 released
Date: Mon, 16 Jun 2003 09:58:03 +0900	[thread overview]
Message-ID: <20030616095803N.hyoshiok@miraclelinux.com> (raw)
In-Reply-To: <200306160044.h5G0i6Su026505@harpo.it.uu.se>

> On Mon, 16 Jun 2003 09:18:46 +0900, Hiro Yoshioka wrote:
> > I just download perfctr 2.5.5 and see the difference
> > between 2.5.4 and 2.5.5 but I could not find code
> > changes except the changelog and todo.
> > 
> > $ diff -u perfctr-2.5.4 perfctr-2.5.5
> > diff -u perfctr-2.5.4/CHANGES perfctr-2.5.5/CHANGES
> > --- perfctr-2.5.4/CHANGES       2003-06-01 21:32:45.000000000 +0900
> > +++ perfctr-2.5.5/CHANGES       2003-06-16 07:11:23.000000000 +0900
> 
> Missing '-r' option to diff, so it only diffs the toplevel files.
> Use diff -ruN to compare two directories recursively.

Thanks for your quick help.

I have made a patch for perfctr 2.5.5 of hardmeter which 
is a memory profiling tool using Intel P4's PEBS (precise
event based sampling) hardware monitoring facility.

See the following patch.

http://cvs.sourceforge.jp/cgi-bin/viewcvs.cgi/hardmeter/hardmeter/patch/perfctr-2.5.5.dif?rev=1.1&content-type=text/vnd.viewcvs-markup

https://sourceforge.jp/projects/hardmeter/
(some pages are written in Japanese)

Regards,
  Hiro
--
Hiro Yoshioka/CTO, Miracle Linux
mailto:hyoshiok@miraclelinux.com
http://www.miraclelinux.com

  reply	other threads:[~2003-06-16  1:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-16  0:44 [Perfctr-devel] perfctr-2.5.5 released mikpe
2003-06-16  0:58 ` Hiro Yoshioka [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-06-15 22:29 mikpe
2003-06-16  0:18 ` [Perfctr-devel] " 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=20030616095803N.hyoshiok@miraclelinux.com \
    --to=hyoshiok@miraclelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mikpe@csd.uu.se \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.