| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
| |
It is partially covered by new code and partially by new CPUs.
PR: 195016
Submitted by: tobias.rehbein@web.de
|
|
|
|
| |
MFC after: 1 week
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use MADT to match ACPI Processor objects to CPUs. MADT and DSDT/SSDTs may
list CPUs in different orders, especially for disabled logical cores. Now
we match ACPI IDs from the MADT with Processor objects, strictly order CPUs
accordingly, and ignore disabled cores. This prevents us from executing
methods for other CPUs, e. g., _PSS for disabled logical core, which may not
exist. Unfortunately, it is known that there are a few systems with buggy
BIOSes that do not have unique ACPI IDs for MADT and Processor objects. To
work around these problems, 'debug.acpi.cpu_unordered' tunable is added.
Set this to a non-zero value to restore the old behavior.
Many thanks to jhb for pointing me to the right direction and the manual
page change.
Reported by: Harris, James R (james dot r dot harris at intel dot com)
Tested by: Harris, James R (james dot r dot harris at intel dot com)
Reviewed by: jhb
MFC after: 1 month
|
|
|
|
|
|
|
|
|
|
| |
list CPUs in different orders, especially for disabled logical cores. Now
we match ACPI IDs from the MADT with Processor objects, strictly order CPUs
accordingly, and ignore disabled cores. This prevents us from executing
methods for other CPUs, e. g., _PSS for disabled logical core, which may not
exist. Unfortunately, it is known that there are a few systems with buggy
BIOSes that do not have unique ACPI IDs for MADT and Processor objects. To
work around these problems
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
| |
"hw.acpi.remove_interface".
|
|
|
|
|
| |
incomplete. If FADT says the register is available, enable the capability
by default. Remove the previous default value from acpi(4).
|
|
|
|
|
| |
PR: docs/147180
Submitted by: Tobias Rehbein
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
has it compiled in, it will be rejected with "module acpi already present!"
and no strange behavior.
MFC after: 1 day
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- "Ns No" is redundant, so reduce it to just "Ns";
- use Li to mark up CPU and system power states because here they are
just strings to be typed literally (add more such mark-up as well);
- the best practice of typesetting tells us to use an en-dash to
indicate a closed range; fortunately, groff_char(7) provides such a symbol.
In addition, consistently use a comma between independent clauses
coordinated by a conjunction.
Pointed out by: ru (mark-up part)
MFC after: 3 days
|
|
|
|
|
|
| |
Add a workaround for conflicts between ACPI Cx CPU idling and LAPIC timer.
MFC after: 1 day
|
|
|
|
|
|
| |
because I forgot to on the last change.
MFC after: 1 day
|
|
|
|
| |
more sense than under hw.acpi. Also, document this in the man page.
|
|
|
|
|
|
| |
PR: 93429
Submitted by: Michaël Grünewald <michael.grunewald@laposte.net>
MFC after: 3 days
|
|
|
|
|
|
| |
Reviewed by: njl
Approved by: cognet (mentor)
MFC after: 3 days
|
|
|
|
|
|
|
|
|
|
| |
s/SYSCTLS/SYSCTL VARIABLES/
s/TUNABLES/LOADER TUNABLES/
s/CAVEAT/CAVEATS/
s/DESCIPTION/DESCRIPTION/
Reviewed by: ru
MFC after: 3 days
|
|
|
|
| |
Approved by: re
|
| |
|
|
|
|
|
|
| |
PR: 77693
Tested/submitted by: John Prather <jprather@axon.cdc.uci.edu>
MFC: 1 day
|
| |
|
| |
|
| |
|
|
|
|
| |
MFC after: 3 days
|
| |
|
| |
|
|
|
|
| |
document some debug output variables, etc. Mdoc assistance welcome.
|
|
|
|
|
|
|
| |
one will never be supported on the same platform, this does not hurt
debugging.
MFC after: 3 days
|
|
|
|
|
|
|
| |
Also reorder tunables.
Approved by: njl
MFC after: 1 week
|
|
|
|
| |
MFC after: 3 days
|
| |
|
|
|
|
|
| |
Reviewed by: ru
Approved by: njl
|
|
|
|
| |
Approved by: njl
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
after. Unify the paths for all Cx states. Remove cpu_idle_busy and
instead do the little profiling we need before re-enabling interrupts.
Use 1 quantum as estimate for C1 sleep duration since the timer interrupt
is the main reason we wake.
While here, change the cx_history sysctl to cx_usage and report statistics
for which idle states were used in terms of percent. This seems more
intuitive than counters. Remove the cx_stats structure since it's no
longer used. Update the man page.
Change various types which do not need explicit size.
|
|
|
|
|
| |
C2, ... Update power_profile to use the new format. Update the
man page to reflect this and give more info on Cx states.
|
| |
|
|
|
|
|
|
| |
Also, disable quirks if booting with a custom DSDT. Add a quirk
to disable loading ACPI so known bad systems can be completely
blacklisted.
|
|
|
|
|
|
| |
Sort acpi debug values. Change "disable" to "disabled" to match rest of
the kernel. Remove debugging from acpi_toshiba since it was only used for
probe/attach.
|
| |
|
|
|
|
| |
"all" value.
|
|
|
|
|
|
| |
/boot/loader.conf. Make the description flow a bit better.
Complaints by: Nate Lawson <nate@root.org>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
device.hints kernel environment variables when disabling ACPI.
Some users are getting confused when they see hint.acpi.0.disabled.
They are confusing it with a sysctl MIB.
Finally, add a reference for device.hints(5) and kenv(1)
in the "SEE ALSO" section of the man page.
PR: docs/62974
Submitted by: Christian S.J. Peron <maneo@bsdpro.com>
|
|
|
|
|
|
|
|
|
|
| |
is reserved by the loader, and thus any tunable name with that suffix will
be silently discarded.
Document this in the header and man page so that other developers do not
develop so many bumps on the head after banging it against the wall.
Detective work by: Mark Santcroos, grehan
|
|
|
|
| |
Pointed out by: Ducrot Bruno (Linux)
|