[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200611151748.05989.ak@suse.de>
Date: Wed, 15 Nov 2006 17:48:05 +0100
From: Andi Kleen <ak@...e.de>
To: discuss@...-64.org
Cc: William Cohen <wcohen@...hat.com>,
Eric Dumazet <dada1@...mosbay.com>,
Andrew Morton <akpm@...l.org>,
Komuro <komurojun-mbn@...ty.com>,
Ernst Herzberg <earny@...4u.de>,
Andre Noll <maan@...temlinux.org>,
oprofile-list@...ts.sourceforge.net,
Jens Axboe <jens.axboe@...cle.com>,
linux-usb-devel@...ts.sourceforge.net, phil.el@...adoo.fr,
Adrian Bunk <bunk@...sta.de>, Ingo Molnar <mingo@...hat.com>,
Alan Stern <stern@...land.harvard.edu>,
linux-pci@...ey.karlin.mff.cuni.cz,
Stephen Hemminger <shemminger@...l.org>,
Prakash Punnoor <prakash@...noor.de>,
Len Brown <len.brown@...el.com>,
Alex Romosan <romosan@...orax.lbl.gov>,
Linus Torvalds <torvalds@...l.org>, gregkh@...e.de,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"Eric W. Biederman" <ebiederm@...ssion.com>,
Andrey Borzenkov <arvidjaar@...l.ru>
Subject: Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)
> OProfile has a simplistic view of the performance monitoring hardware. The
> routines in libop/op_alloc_counter.c determine what set of performance registers
> is available from the processor in use. There is no check to see what registers
> are actually available in the /dev/oprofile directory.
>
> opcontrol executes ophelp to determine which specific counters to count which
> events. The function map_event_to_counter() in libop/op_alloc_counter.c does the
> actual selection. It seems what is needed is for map_event_to_counter() to check
> to see which counters are available and mark the others as unavailable
Thanks for the explanation. Can you please fix it and release a new version?
Documentation/Changes could be adapted then.
-Andi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists