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  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]
Date:	Sun, 5 Jan 2014 09:59:49 -0800
From:	Andi Kleen <>
To:	Alexander Gordeev <>
	Arnaldo Carvalho de Melo <>,
	Jiri Olsa <>, Ingo Molnar <>,
	Frederic Weisbecker <>,
	Peter Zijlstra <>,
	Andi Kleen <>
Subject: Re: [PATCH RFC v2 0/4] perf: IRQ-bound performance events

On Sat, Jan 04, 2014 at 07:22:32PM +0100, Alexander Gordeev wrote:
> Hello,
> This is version 2 of RFC "perf: IRQ-bound performance events". That is an
> introduction of IRQ-bound performance events - ones that only count in a
> context of a hardware interrupt handler. Ingo suggested to extend this
> functionality to softirq and threaded handlers as well:

Did you measure the overhead in workloads that do a lot of interrupts?
I assume two WRMSR could be a significant part of the cost of small interrupts.

For counting at least it would be likely a lot cheaper to just RDPMC
and subtract manually.

The cache miss example below is certainly misleading, as cache misses
by interrupts are often a "debt", that is they are forced on whoever
is interrupted. I don't think that is a good use of this.

I guess it can be useful for cycles.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists