On Wed, Nov 02, 2016 at 06:28:08PM +0200, Konstantin Belousov wrote:
> On Wed, Nov 02, 2016 at 09:18:15AM -0700, Jason Harmening wrote:
> > I think you are probably right. Hacking out the Intel-specific
> > additions to C-state parsing in acpi_cpu_cx_cst() from r282678 (thus
> > going back to sti;
On Fri, Nov 25, 2016 at 1:25 AM, Konstantin Belousov
wrote:
> On Wed, Nov 02, 2016 at 06:28:08PM +0200, Konstantin Belousov wrote:
> > On Wed, Nov 02, 2016 at 09:18:15AM -0700, Jason Harmening wrote:
> > > I think you are probably right. Hacking out the Intel-specific
> > > additions to C-state
Hello,
Since I'm running this CPU, I've noticed there is additional
field in supported frequency (under heavy load)-
dev.cpu.0.cx_supported: C1/1/1 C2/2/1 C3/3/57
dev.cpu.0.freq_levels: 2801/35000 2800/35000 2450/30625 2133/23888
1866/20902 1600/15000 1400/13125 1200/11250 1000/9375 800/12000 70
the acpi cpu frequency module just exposes the frequency lis given to
it by ACPI. If your ACPI table exposes the turbo boost frequency but
doesn't implement it on the backend, FreeBSD doesn't know. We just
obey what we're told. :)
-a
On 25 November 2016 at 20:16, Jakub Lach wrote:
> Hello,
>
>
Thanks for reply! If I've understood you correctly, that means the ACPI
table somehow provides (lists) turbo mode for this CPU even though it does
not support it [1]? Is there a way to check it's real speed under load?
I'm guessing no. [1] ark.intel.com ark.intel.com
Problemas com a mensagem? visualize no navegador. Só
Hoje! Black Friday! Pizza de Mussarella de R$ 34,90 por R$ 24,90!
www.morumbimaster.com.brUnidade Morumbi: Avenida Giovanni
Gronchi , 2099, Morumbi, São Paulo, SP.Telefone: (011) 3742-1933 -
(011) 4117-0284 - What´s (011) 98
