Re: [patch 0/1] extending low-level markers

> > > > > > > The locking is internal to our framework and done on a per-type basis. > > The start/end example i mentioned could represent an interval. When the > > two points are wired up they both have their private data pointing at a > > kmalloc'd interval structure internal to our framework,

Re: [patch 0/1] extending low-level markers

> Hrm, what is wrong with : > > trace_mark(ds_myevent, "%d %zu %p", arg1, arg2, arg3); > > then ? > > You could then attach your probe to all markers staring with a ds_ > prefix. (we should keep a list of the used prefixes somewhere) You could > match with format strings to figure out which call

Re: [patch 0/1] extending low-level markers

On 02/08/07 12:44 -0400, Mathieu Desnoyers wrote: > * [EMAIL PROTECTED] ([EMAIL PROTECTED]) wrote: > > Mathieu > > > > I have been working with your Kernel Markers infrastructure now for some > > time and have run into an extendability issue. > > Hi Noah, > > Can you tell us a little bit more ab

Re: 2.6.23-rc1 -- build failure

Thanks this fixed it. My LKML search didn't find this patch. -noah On 7/25/07, Len Brown <[EMAIL PROTECTED]> wrote: On Wednesday 25 July 2007 12:11, Noah Watkins wrote: > Latest git tree gives following build errors (config attached): > > make -C /yggnfs/nwatkins/kernels/git

[PATCH -rt] whitespace cleanup for 2.6.20-rc5-rt7

fixes trailing whitespace and spaces before tab indents in 2.6.20-rc5-rt7 as reported with: git-apply --whitespace=error-all --- arch/arm/mach-omap1/time.c|2 +- arch/i386/kernel/entry.S |2 +- arch/i386/kernel/reboot.c |2 +- arch/ia64/Kconfig

[PATCH] include linux/fs.h in linux/cdev.h for struct inode

--- include/linux/cdev.h |1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/include/linux/cdev.h b/include/linux/cdev.h index f309b00..b53e2a0 100644 --- a/include/linux/cdev.h +++ b/include/linux/cdev.h @@ -5,6 +5,7 @@ #include #include #include +#include struct cd