Re: Leaving the Desktop Market

Am 04.05.2014 11:28, schrieb Marko Zec:
> On Sun, 4 May 2014 01:13:48 -0700
> Adrian Chadd <adrian@freebsd.org> wrote:
> 
>> [snip]
>>
>> ok, how about this to start with:
>>
>> http://people.freebsd.org/~adrian/power/20140504-powerd-1.diff
>>
>> This defaults powerd to set minfreq to 50% of the hardware available
>> maxfreq, unless minfreq is explicitly given on the command line.
> 
> As already noted earlier in this thread, if you disable
> 
> hint.p4tcc.0.disabled=1
> hint.acpi_throttle.0.disabled=1
> 
> then the kernel does not even expose expose those silly minimum
> "frequencies", and your problem goes away without patching powerd.
> 
> A more reasonable and simpler patch would be to disable the two
> offending throttling drivers by default, I really cannot see a single
> reason why do we need them at all, less why they are enabled.
> 
> Marko

Very true and this topic has come up so many times during for at least a
decade (if not much longer). Throttling had its use at a time, but
this time is long gone.

Throttling is enabled unless probing of the "p4tcc" and "acpi_throttle"
pseudo-devices is disabled by device hints.

As a first step, these hints could be set in /boot/defaults/loader.conf.
They could still be overridden in /boot/loader.conf, if they really are
required (anybody still got P4 systems running -CURRENT?).

A better fix would be to disable throttling depending on the CPU model
identified (or on the presence of any other power management solution).

Since the CPUs are probed before any device, adding a "disable" hint
for both throttling methods would be kind of a hack, but should work.

If there is an agreement, that we should move into that direction, I'll
try to create a patch for review.

Regards, STefan
_______________________________________________
freebsd-hackers@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"