linux-kernel - Re: [PATCH] x86, perfctr: remove unused func avail_to_resrv_perfctr

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: <20091228100020.GA730@elte.hu>
Date:	Mon, 28 Dec 2009 11:00:20 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Cyrill Gorcunov <gorcunov@...il.com>
Cc:	Naga Chumbalkar <nagananda.chumbalkar@...com>, x86@...nel.org,
	linux-kernel@...r.kernel.org, oprofile-list@...ts.sf.net,
	tglx@...utronix.de
Subject: Re: [PATCH] x86, perfctr: remove unused func
 avail_to_resrv_perfctr_nmi()


* Cyrill Gorcunov <gorcunov@...il.com> wrote:

> > Not that i know of.
> 
> ok, then we could apply this patch I think, at least for a while.

yeah, i have applied it.

> > In fact we should transform/migrate the NMI watchdog driver by making it 
> > based on a kernel-internal created perf event. (which is what the NMI 
> > watchdog really is: a periodic NMI event occuring once per second and 
> > running a callback function.)
> 
> Yes, this would be great. I'll try to find out some time for this task, 
> though no promises :) If someone get it done earlier I would really 
> appreciate.

Feel free to do it. We could do it gradual. Maybe we could also then gradually 
remove perfctr code for CPU variants that already have perf events support. 

Plus later on we could carefully identify bits of APIC support code in 
perfctr.c and turn those into minimal perf events PMU drivers.

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