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
This commit is contained in:
parent
a7b5acac1a
commit
bf7f8bd30a
@ -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
|
||||
|
Loading…
Reference in New Issue
Block a user