linux-kernel - [PATCH 0/1] Hardware Latency Detector (formerly SMI detector)

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

Date:	Thu, 11 Jun 2009 00:58:29 -0400
From:	Jon Masters <jonathan@...masters.org>
To:	linux-kernel@...r.kernel.org
Cc:	akpm@...ux-foundation.org, tglx@...utronix.de, mingo@...e.hu,
	rostedt@...dmis.org
Subject: [PATCH 0/1] Hardware Latency Detector (formerly SMI detector)

Hi folks,

Please find attached my second re-write of the SMI detector, now called the
Hardware Latency Detector. This is a loadable module that grabs the CPU for
configurable periods of time (all under stop_machine()) and samples the TSC
looking for discontinuity. If observed latencies exceed a threshold (for
example caused by an System Management Interrupt or similar) then the
event is recorded in a global ring_buffer, readable via debugfs.

The previous version was too x86-centric, since there is no reason one could
not also use this newly renamed hwlat_detector on any supported platform with
some kind of underlying firmware/virtualization issues effecting observable
system latency measurements.

Thanks to akpm and others for feedback comments so far.

Changes since the previous version:

- Renamed to hwlat_detector
- Followed Andrew's cleanup advice
- Rewritten the documentation

Jon.
--
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/