Revision tags: v6.2.1, v6.2.0, v6.3.0, v6.0.1, v6.0.0, v6.0.0rc1, v6.1.0, v5.8.3, v5.8.2, v5.8.1, v5.8.0, v5.9.0, v5.8.0rc1, v5.6.3, v5.6.2, v5.6.1, v5.6.0, v5.6.0rc1, v5.7.0, v5.4.3, v5.4.2 |
|
#
fcf6efef |
| 02-Mar-2019 |
Sascha Wildner <saw@online.de> |
kernel: Remove numerous #include <sys/thread2.h>.
Most of them were added when we converted spl*() calls to crit_enter()/crit_exit(), almost 14 years ago. We can now remove a good chunk of them agai
kernel: Remove numerous #include <sys/thread2.h>.
Most of them were added when we converted spl*() calls to crit_enter()/crit_exit(), almost 14 years ago. We can now remove a good chunk of them again for where crit_*() are no longer used.
I had to adjust some files that were relying on thread2.h or headers that it includes coming in via other headers that it was removed from.
show more ...
|
Revision tags: v5.4.1, v5.4.0, v5.5.0, v5.4.0rc1, v5.2.2, v5.2.1 |
|
#
704d2129 |
| 29-Apr-2018 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Refactor machdep.cpu_idle_hlt
* Refactor machdep.cpu_idle_hlt. Operation works essentially the same way as before but the code is a lot easier to read.
* Refactor mode 3 to have ACPI ca
kernel - Refactor machdep.cpu_idle_hlt
* Refactor machdep.cpu_idle_hlt. Operation works essentially the same way as before but the code is a lot easier to read.
* Refactor mode 3 to have ACPI call back into machdep when entering a C1 halt. Continue using HLT for this situation as we aren't really sure what ACPI may or may not have done. MONITOR/MWAIT might not be appropriate.
* Fix bug in cpu_smp_stopped(). Just because cpu_mwait_hints is non-zero does not mean that there is an index entry for CPU_MWAIT_C1. Use the last entry based on cpu_mwait_hints instead.
* Note that machdep.cpu_idle_hlt mode 2 still doesn't work as intended.
show more ...
|
Revision tags: v5.2.0, v5.3.0, v5.2.0rc |
|
#
df21e16d |
| 28-Jan-2018 |
Imre Vadász <imre@vdsz.com> |
acpi - Use KOBJ_GPRI_ACPI driver priorities for ig4 and gpio_intel.
* Since we currently don't handle the ACPI _DEP methods appropriately, use the "global priority hack" from 5025fc65cd2448de8a5
acpi - Use KOBJ_GPRI_ACPI driver priorities for ig4 and gpio_intel.
* Since we currently don't handle the ACPI _DEP methods appropriately, use the "global priority hack" from 5025fc65cd2448de8a5b7295c9936b473a7b0194 to enforce that ig4 and gpio_intel attach before various ACPI namespace devices.
* This uses the KOBJ_GPRI_ACPI+1 and KOBJ_GPRI_ACPI+2 driver global priority levels for important ACPI drivers, which may have to attach before other ACPI devices can be used.
* This also adds the KOBJ_GPRI_ACPI global priority level to the sdhci_acpi driver declaration.
show more ...
|
#
5025fc65 |
| 16-Jan-2018 |
Matthew Dillon <dillon@apollo.backplane.com> |
kernel - Add a global priority hack for ACPI
* Allows ACPI to fully probe and attach all acpi devices before attaching any non-ACPI devices.
* May improve device attach stability.
* Currently on
kernel - Add a global priority hack for ACPI
* Allows ACPI to fully probe and attach all acpi devices before attaching any non-ACPI devices.
* May improve device attach stability.
* Currently only implemented at the top-level of the acpi device tree.
show more ...
|
Revision tags: v5.0.2, v5.0.1, v5.0.0, v5.0.0rc2, v5.1.0, v5.0.0rc1, v4.8.1 |
|
#
0e4ac8cf |
| 27-Mar-2017 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
kern: Add per-cpu helper threads, which handles lwkt messages.
They will be used to avoid netisr abusing.
|
Revision tags: v4.8.0, v4.6.2, v4.9.0, v4.8.0rc, v4.6.1, v4.6.0, v4.6.0rc2, v4.6.0rc, v4.7.0, v4.4.3, v4.4.2, v4.4.1, v4.4.0, v4.5.0, v4.4.0rc, v4.2.4, v4.3.1, v4.2.3, v4.2.1, v4.2.0 |
|
#
90a26aa2 |
| 19-Jun-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Allow forcing busmastering status and arbitration for C3
|
Revision tags: v4.0.6, v4.3.0, v4.2.0rc, v4.0.5 |
|
#
f77673be |
| 16-Mar-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
Revert "acpi/cstate: Detect and fix duplicated C-states"
This reverts commit 4221f7280cb32cbd2292001d52653e01a71872c9.
Looks like it is intentional to avoid bus mastering register accessing, cache
Revert "acpi/cstate: Detect and fix duplicated C-states"
This reverts commit 4221f7280cb32cbd2292001d52653e01a71872c9.
Looks like it is intentional to avoid bus mastering register accessing, cache flush, and changing interrupt timer, which is required for C3.
show more ...
|
#
daa63909 |
| 16-Mar-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Match C-states of the hyperthreads on the same core
Some stupid BIOSes set different C-states for hyperthreads on the same core, which prevents the core from entering deep C-states, sin
acpi/cstate: Match C-states of the hyperthreads on the same core
Some stupid BIOSes set different C-states for hyperthreads on the same core, which prevents the core from entering deep C-states, since not all hyperthreads of the core are in the deep C-states.
We fix this by using same number of C-states for hyperthreads on the same core; the hyperthread w/ more C-states is taken as master.
show more ...
|
#
02bba4e7 |
| 15-Mar-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Clear saved C-state softc, if attach failed
And install softc during the probe; instead of using (void *)1.
|
#
4221f728 |
| 15-Mar-2015 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Detect and fix duplicated C-states
Some buggy BIOSes create two C2 states, however, the latter one is obviously C3. Add tunable hw.acpi.cpu.cst.check_duplicated to detect and fix this
acpi/cstate: Detect and fix duplicated C-states
Some buggy BIOSes create two C2 states, however, the latter one is obviously C3. Add tunable hw.acpi.cpu.cst.check_duplicated to detect and fix this bug; it is not enabled by default.
show more ...
|
Revision tags: v4.0.4, v4.0.3, v4.0.2, v4.0.1 |
|
#
9d1f0c52 |
| 15-Nov-2014 |
Sascha Wildner <saw@online.de> |
kernel: Refer to it as "ACPICA", not "ACPI CA" or "ACPI-CA".
|
Revision tags: v4.0.0, v4.0.0rc3, v4.0.0rc2, v4.0.0rc, v4.1.0, v3.8.2, v3.8.1, v3.6.3, v3.8.0, v3.8.0rc2, v3.9.0, v3.8.0rc, v3.6.2, v3.6.1 |
|
#
3c0c7751 |
| 08-Feb-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Remove unnecessary bus_generic_{attach,probe}()
They were inheritted when acpi_cpu_cstate.c was splitted from acpi_cpu.c. C-state is a leaf device, nothing will be its children.
|
#
e80ea409 |
| 01-Feb-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
cputimer/intr: Move powersaving intr cputimer switching to kern_cputimer.c
While I'm here fix several bugs: - Don't take ERESTART as error - Use serializer to protect the number of power saving requ
cputimer/intr: Move powersaving intr cputimer switching to kern_cputimer.c
While I'm here fix several bugs: - Don't take ERESTART as error - Use serializer to protect the number of power saving request. Using atomic_fetchadd_int is not enough here: The first power saving request could fail. However, before its failure, other power saving request could be successful, since the intr cputimer switch is skipped.
show more ...
|
#
41d9045e |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cpu: Remove the cpux naming hack
Used to avoid name conflict between C-state module and cpu module
|
#
5764e125 |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate/x86_64: Implement native C-state support for Intel CPUs
The native C-state on Intel CPUs is entered using monitor/mwait w/ the help from mwait hint (eax) and extension (ecx, break upon i
acpi/cstate/x86_64: Implement native C-state support for Intel CPUs
The native C-state on Intel CPUs is entered using monitor/mwait w/ the help from mwait hint (eax) and extension (ecx, break upon interrupt).
We still need to keep an eye on native C1 state. Currently C1 state only uses "sti;halt".
show more ...
|
#
6df05d3d |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Allow fixed hardware GAS for C1, which means "sti;halt"
Add comment we still need to filter Intel's "C1 I/O then halt". It probably won't be problem, since the related bit is not set i
acpi/cstate: Allow fixed hardware GAS for C1, which means "sti;halt"
Add comment we still need to filter Intel's "C1 I/O then halt". It probably won't be problem, since the related bit is not set in _OSC or _PDC.
show more ...
|
#
18862f87 |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Fix resource leakage
|
#
48272d39 |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Use boolean_t for acpi_cst_disable_idle
|
#
9925408f |
| 30-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Rework preamble operation for entering C-state
- Save preamble operation in C-state struct, instead of choosing preamble operation at run time - Add machine depend C-state setup code
acpi/cstate: Rework preamble operation for entering C-state
- Save preamble operation in C-state struct, instead of choosing preamble operation at run time - Add machine depend C-state setup code to optimize out certain preamble operation for various CPU vendors - Fix up generic preamble operation setup according to ACPI spec
show more ...
|
#
24da862f |
| 27-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Add a method to per C-state softc to enter the C-state
This will be used to add "native" C-state support
|
#
e24a50d0 |
| 27-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Make sure that idle hook is installed as the last step
|
#
7eb26369 |
| 27-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: If there is bus master activity pick up non-C3 is enough
Since bus master activity is only checked before entering C3+ states.
|
#
ad544345 |
| 27-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Rearrange _CST reprobe code path
|
#
1dff7e06 |
| 27-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Save ACPI_GENERIC_ADDRESS for later use
Also fix a bug that 'res_type' should be used instead of 'type' during FADT C state resource allocation.
|
#
a1116831 |
| 26-Jan-2014 |
Sepherosa Ziehau <sephe@dragonflybsd.org> |
acpi/cstate: Function/variable/macro renaming
Adjust some comment. No functional changes.
|