summaryrefslogtreecommitdiffstats
path: root/share/man/man4/est.4
diff options
context:
space:
mode:
authorsbruno <sbruno@FreeBSD.org>2012-06-19 17:13:14 +0000
committersbruno <sbruno@FreeBSD.org>2012-06-19 17:13:14 +0000
commite551b0ecfb98653b427343a9dc4e018566a78913 (patch)
treee1105c91e19ff52352c84b4e9d501a2a106185d8 /share/man/man4/est.4
parentec398928923afa6edd4aa8ada94387db8950b61e (diff)
downloadFreeBSD-src-e551b0ecfb98653b427343a9dc4e018566a78913.zip
FreeBSD-src-e551b0ecfb98653b427343a9dc4e018566a78913.tar.gz
Correct misunderstanding of hw.est.strict
Setting strict causes a validation of the requested value vs the value currently running after a frequency change is requested. Change applicability to be single core not i386. Thanks to mav@ for reviewing and commenting on my lack of understanding. MFC after: 2 weeks
Diffstat (limited to 'share/man/man4/est.4')
-rw-r--r--share/man/man4/est.44
1 files changed, 2 insertions, 2 deletions
diff --git a/share/man/man4/est.4 b/share/man/man4/est.4
index 618e5a5..f1b5832 100644
--- a/share/man/man4/est.4
+++ b/share/man/man4/est.4
@@ -66,8 +66,8 @@ Attempt to infer information from direct probing of the msr.
Should only be used in diagnostic cases
.Pq default 0
.It hw.est.strict
-Do not allow different cpus to be set to different frequencies.
-It appears that this will only work on i386 systems
+Validate frequency requested is accepted by the cpu when set.
+It appears that this will only work on single core cpus.
.Pq default 0
.El
.Sh DIAGNOSTICS
OpenPOWER on IntegriCloud