From eb8f3e776c9aad605af35a2b1ae73b62b8b45f0b Mon Sep 17 00:00:00 2001 From: Charles Blake Date: Fri, 3 May 2024 10:41:46 -0400 Subject: [PATCH] Soften claim from all -> much of since no one knows what accuracy may be needed in the end. --- doc/tim.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/doc/tim.md b/doc/tim.md index 161397c..705352a 100644 --- a/doc/tim.md +++ b/doc/tim.md @@ -185,8 +185,8 @@ There are many such actions..1) Shutting down browsers 2) Going single-user 3) `taskset`/`chrt`, 4) fixing CPU frequency dynamically in-OS 5) Rebooting into a BIOS with fixed freq CPU(s) (or your OS's equiv. of these Linux interventions), 6) `isolcpus` to avoid timer interrupts entirely, 7) Cache Allocation Technology -extensions to reserve L3, and on & on. (`tim` hopes that simpler ideas can -prevent all that effort most of the time without corrupting benchmark design.) +extensions to reserve L3, and on & on. (`tim` hopes simpler ideas can prevent +much of that effort most of the time without corrupting benchmark design.) [^1]: Find a link to circa 2019 blog about writing own "Measurement OS" to study how [Spectre](https://en.wikipedia.org/wiki/Spectre_(security_vulnerability))-