linux-kernel - Re: Perf events/ARM

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] [day] [month] [year] [list]

Message-ID: <20091201145305.GC4061@wear.picochip.com>
Date:	Tue, 1 Dec 2009 14:53:05 +0000
From:	Jamie Iles <jamie@...ieiles.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...e.hu>, Jamie Iles <jamie@...ieiles.com>,
	Paul Mackerras <paulus@...ba.org>, linux-kernel@...r.kernel.org
Subject: Re: Perf events/ARM

Pete, Ingo,

On Tue, Dec 01, 2009 at 03:40:44PM +0100, Peter Zijlstra wrote:
> Things like wakeups and ->event_limit might get delayed.
> 
> Delayed wakeups can be mitigated by larger buffers, delayed disable on
> ->event_limit is not something you can fix up.
> 
> Does your PMU generate regular interrupts or actual NMIs? If its normal
> interrupts you can simply call perf_event_do_pending() at the
> pmu-interrupt tail.
The PMU generates regular interrupts and in the case of the platform I'm
working on these go to a regular vectored interrupt controller all sharing the
same vector. So I'll add a call to perf_event_do_pending() at the tail of the
PMU IRQ and leave set_perf_event_pending() as a nop.

Thanks,

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