> Actually it has 4 cores and 8 threads. In xenpm's output, there're 2 lines
> saying '[CPUx] failed to get cpufreq parameter', 'x' being 1 and 3.
This is a bug in xenpm when 'smt' is off, as discussed in here:
https://github.com/QubesOS/qubes-issues/issues/4456
Still need help with turbo
On Wednesday, December 19, 2018 at 12:10:19 AM UTC-5, awokd wrote:
> I think xenpm is supposed to work the best. Qubes disables SMT for
> security, so if you only have 2 real cores that's all you'll see.
Actually it has 4 cores and 8 threads. In xenpm's output, there're 2 lines
saying '[CPUx]
qubesuserma...@gmail.com:
The most promising result is given by xenpm, however only info of 2 cores out
of 4 are listed.
I think xenpm is supposed to work the best. Qubes disables SMT for
security, so if you only have 2 real cores that's all you'll see.
--
You received this message because
The most promising result is given by xenpm, however only info of 2 cores out
of 4 are listed.
--
You received this message because you are subscribed to the Google Groups
"qubes-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to
