linux-kernel - Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061116213209.GB19306@frankl.hpl.hp.com>
Date:	Thu, 16 Nov 2006 13:32:09 -0800
From:	Stephane Eranian <eranian@....hp.com>
To:	William Cohen <wcohen@...hat.com>
Cc:	Andi Kleen <ak@...e.de>, 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>,
	Adrian Bunk <bunk@...sta.de>,
	linux-usb-devel@...ts.sourceforge.net, phil.el@...adoo.fr,
	Eric Dumazet <dada1@...mosbay.com>,
	Ingo Molnar <mingo@...hat.com>,
	Alan Stern <stern@...land.harvard.edu>,
	linux-pci@...ey.karlin.mff.cuni.cz,
	Prakash Punnoor <prakash@...noor.de>,
	"Eric W. Biederman" <ebiederm@...ssion.com>,
	Len Brown <len.brown@...el.com>,
	Alex Romosan <romosan@...orax.lbl.gov>,
	Linus Torvalds <torvalds@...l.org>, discuss@...-64.org,
	gregkh@...e.de,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Stephen Hemminger <shemminger@...l.org>,
	Andrey Borzenkov <arvidjaar@...l.ru>
Subject: Re: [discuss] Re: 2.6.19-rc5: known regressions (v3)

Hello,

On Thu, Nov 16, 2006 at 10:34:56AM -0500, William Cohen wrote:
> 
> Is this going to require sharing the nmi interrupt and knowing which perfcounter 
> register triggered the interrupt to get the correct action?  Currently the 
> oprofile interrupt handler assumes any performance monitoring counter it sees 
> overflowing is something it should count.
> 
Yes, you need to share the NMI interrupt. In my next perfmon patch you will
see that this can be made to work. You just need to add one check in the 
NMI handler callback: is it for me or else try perfmon? Perfmon can auto-detect
if NMI is active and give up the right counter (there is an API to check
what is reserved). The interface propagates the list of available counters
to apps which then pass the information onto libpfm which tries to use
the remaining counters.

-- 
-Stephane
-
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/