public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
To: penberg@cs.helsinki.fi
Cc: compudj@krystal.dyndns.org, linux-kernel@vger.kernel.org,
	righi.andrea@gmail.com, eduard.munteanu@linux360.ro,
	Tom Zanussi <tzanussi@gmail.com>
Subject: [ANNOUNCE] kmemtrace-user repo update
Date: Wed, 24 Sep 2008 00:29:14 +0300	[thread overview]
Message-ID: <20080923212914.GB5237@localhost> (raw)

Hi everybody,

This concerns...
http://repo.or.cz/w/kmemtrace-user.git

kmemtrace-user's git repo has been update. This is the last revision
history alteration. Due to missing copyright notices and other problems,
I preferred to keep things clean.

So now you need to git-clone it again, but it will no longer be
necessary in the future. 

Changes:
- Refactored code, it's a lot cleaner now.
- It now works on 32-bit machines, or at least I hope so: it no longer
  exhibits problems when the userspace is compiled with the -m32 flag.
- We now use mmap() for almost anything.
- kmemtraced copies /proc/kallsyms, so if you want to hack on
  kmemtrace-report, you no longer need to do all stuff on a
  kmemtrace-enabled kernel.
- Probably other misc janitorial stuff.

Priority todos:
- Integrate Tom's UTT patch (thanks again). I'd first like to provide a UTT
  wrapper in the kernel to provide all those files without having to
  explicitly code things in kmemtrace.
- Make it work cross-arch (endianness etc.).

Kinda lower priority todos:
- Add timestamps. Useful to measure allocations' lifetimes in a tangible
  way.


Please take a shot at this and let me know what you think.


	Cheers,
	Eduard


             reply	other threads:[~2008-09-23 21:29 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-23 21:29 Eduard - Gabriel Munteanu [this message]
     [not found] ` <1223386477.28348.42.camel@penberg-laptop>
     [not found]   ` <1223623191.8959.26.camel@penberg-laptop>
     [not found]     ` <1223628687.8959.37.camel@penberg-laptop>
     [not found]       ` <1223629803.8959.40.camel@penberg-laptop>
2008-10-10  9:42         ` [PROBLEM] hard-lock with kmemtrace, relayfs, and splice Pekka Enberg
2008-10-10 11:51           ` Eduard - Gabriel Munteanu
2008-10-11  4:58           ` Tom Zanussi
2008-10-11 18:17             ` Eduard - Gabriel Munteanu
2008-10-13  6:57             ` Pekka Enberg
2008-10-14  4:03               ` Tom Zanussi
2008-10-14  5:13                 ` Pekka Enberg
2008-10-14  5:46                   ` Tom Zanussi
2008-10-14  6:58                     ` Pekka Enberg
2008-10-14  7:30                     ` Eduard - Gabriel Munteanu
2008-10-14  7:05                   ` Pekka Enberg
2008-10-24  4:44           ` Peter Teoh
2008-10-24 14:15             ` Pekka Enberg
2008-10-25  0:56               ` Peter Teoh
2008-10-25 14:04                 ` Eduard - Gabriel Munteanu

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=20080923212914.GB5237@localhost \
    --to=eduard.munteanu@linux360.ro \
    --cc=compudj@krystal.dyndns.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=penberg@cs.helsinki.fi \
    --cc=righi.andrea@gmail.com \
    --cc=tzanussi@gmail.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