On Mon, 12 Jun 2006, Stephane Eranian wrote: > You have to be careful with the versin of libpfm you are using. Due > to additions of system calls, the perfmon syscalls get bumped and > if you have a mismatch between what libpfm knows and what the kernel uses > you get into this situation. > > If you tell me which kernel patch you are using I can tell you which libpfm > to use.
Just pointed out the possible mis-match solved the problem. i was using the 0322 kernel patch to match 2.6.16.20 but had libpfm0522, jumping back to 0322 for libpfm corrected the problem. pfmon-0522 appears to work fine with the older 0322 libpfm. is this ok to do in the long run, or should i always use matching kernal/lib/pfmon versions? are things moving fast enough in development it is worth always using the newest (.17_rc5 currently) patches/libs/tools or is the libpfm userspace api remaining fairly stable? and the in kernel api? thanks for the tip -dwn _______________________________________________ perfmon mailing list [email protected] http://www.hpl.hp.com/hosted/linux/mail-archives/perfmon/
