Fri Aug 11 11:41:15 2006  Søren Sandmann  <sandmann@redhat.com>

	* TODO: Updates
This commit is contained in:
Søren Sandmann
2006-08-11 15:41:46 +00:00
committed by Søren Sandmann Pedersen
parent 2bc1d6f280
commit 060fd343a8
2 changed files with 22 additions and 0 deletions

View File

@ -1,3 +1,7 @@
Fri Aug 11 11:41:15 2006 Søren Sandmann <sandmann@redhat.com>
* TODO: Updates
2006-08-08 Soren Sandmann <ssp@localhost.localdomain> 2006-08-08 Soren Sandmann <ssp@localhost.localdomain>
* sysprof.c (main): Make the load_file() idle low priority to * sysprof.c (main): Make the load_file() idle low priority to

18
TODO
View File

@ -32,6 +32,8 @@ Before 1.0.3:
Before 1.2: Before 1.2:
* Rename stack_stash_foreach_by_address() to stack_stash_foreach_unique()
* Make it compilable against a non-running kernel. * Make it compilable against a non-running kernel.
* commandline version should check that the output file is writable * commandline version should check that the output file is writable
@ -198,6 +200,22 @@ Before 1.2:
return addresses, along with the location on the stack. This return addresses, along with the location on the stack. This
just might be enough for a userspace stack walker. just might be enough for a userspace stack walker.
- Yet another: krh suggests hashing blocks of the stack, then
only sending the blocks that changed since last time.
- every time you send a stackblock, also send a cookie.
- whenever you *don't* send a stackblock, send the cookie
instead. That way you always get a complete stacktrace
conceptually.
- also, that would allow the kernel to just have a simple
hashtable containing the known blocks. Though, that could
become large. Actually there is no reason to store the
blocks; you can just send the hashcode. That way you
would only need to store a list of hashcodes that we
have generated previously.
* If interrupt happens in kernel mode, send both * If interrupt happens in kernel mode, send both
kernel stack and user space stack, have userspace stitch them kernel stack and user space stack, have userspace stitch them
together. well, they could be stitched together in the kernel. together. well, they could be stitched together in the kernel.