|
Revision tags: release/13.4.0-p5, release/13.5.0-p1, release/14.2.0-p3, release/13.5.0, release/14.2.0-p2, release/14.1.0-p8, release/13.4.0-p4, release/14.1.0-p7, release/14.2.0-p1, release/13.4.0-p3, release/14.2.0, release/13.4.0, release/14.1.0, release/13.3.0, release/14.0.0 |
|
| #
685dc743 |
| 16-Aug-2023 |
Warner Losh <[email protected]> |
sys: Remove $FreeBSD$: one-line .c pattern
Remove /^[\s*]*__FBSDID\("\$FreeBSD\$"\);?\s*\n/
|
| #
4d846d26 |
| 10-May-2023 |
Warner Losh <[email protected]> |
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of
spdx: The BSD-2-Clause-FreeBSD identifier is obsolete, drop -FreeBSD
The SPDX folks have obsoleted the BSD-2-Clause-FreeBSD identifier. Catch up to that fact and revert to their recommended match of BSD-2-Clause.
Discussed with: pfg MFC After: 3 days Sponsored by: Netflix
show more ...
|
|
Revision tags: release/13.2.0, release/12.4.0, release/13.1.0, release/12.3.0 |
|
| #
8362905c |
| 17-Nov-2021 |
sadaszewski <[email protected]> |
coretemp: Only log critical temperature events
According to the Intel manual https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-vol-3b-par
coretemp: Only log critical temperature events
According to the Intel manual https://www.intel.com/content/dam/www/public/us/en/documents/manuals/64-ia-32-architectures-software-developer-vol-3b-part-2-manual.pdf the Thermal Status (0) and Thermal Status Log (1) bits report only a high temperature on the CPU, not a critical temperature as suggested in the coretemp driver. Check the Critical Temperature Log (5) instead. The critical temperature waives guarantees of correct function, therefore the CPU could have for example written some wrong values into memory at that point and the OS should be stopped ASAP as the state is no longer reliable.
Reviewed by: imp (confirmed descriptions of bits, linux ignores these bits) Pull Request: https://github.com/freebsd/freebsd-src/pull/562
show more ...
|
| #
b3ed7cc5 |
| 09-May-2022 |
John Baldwin <[email protected]> |
coretemp: Remove unused devclass argument to DRIVER_MODULE.
|
| #
d3a8f98a |
| 25-Sep-2021 |
Alexander Motin <[email protected]> |
Make CPU children explicitly share parent unit numbers.
Before this device unit number match was coincidental and broke if I disabled some CPU device(s). Aside of cosmetics, for some drivers (may b
Make CPU children explicitly share parent unit numbers.
Before this device unit number match was coincidental and broke if I disabled some CPU device(s). Aside of cosmetics, for some drivers (may be considered broken) it caused talking to wrong CPUs.
show more ...
|
| #
4cc6fe1e |
| 02-Aug-2021 |
Konstantin Belousov <[email protected]> |
coretemp: use x86_msr_op for thermal MSR access
Reviewed by: markj Discussed with: mav Sponsored by: The FreeBSD Foundation MFC after: 1 week Differential revision: https://reviews.freebsd.org/D31386
|
| #
74f80bc1 |
| 30-Jul-2021 |
Alexander Motin <[email protected]> |
coretemp(4): Switch to smp_rendezvous_cpus().
Use of smp_rendezvous_cpus() instead of sched_bind() allows to not block indefinitely if target CPU is running some thread with higher priority, while a
coretemp(4): Switch to smp_rendezvous_cpus().
Use of smp_rendezvous_cpus() instead of sched_bind() allows to not block indefinitely if target CPU is running some thread with higher priority, while all we need is single rdmsr/wrmsr instruction call. I guess it should also be much cheaper than full thread migration.
MFC after: 2 weeks Sponsored by: iXsystems, Inc.
show more ...
|
|
Revision tags: release/13.0.0, release/12.2.0 |
|
| #
ef013cee |
| 14-Jul-2020 |
Ryan Moeller <[email protected]> |
hwpmc: Always set pmc_cpuid to something
pmc_cpuid was uninitialized for most AMD processor families. We can still populate this string for unimplemented families.
Also added a CPUID_TO_STEPPING m
hwpmc: Always set pmc_cpuid to something
pmc_cpuid was uninitialized for most AMD processor families. We can still populate this string for unimplemented families.
Also added a CPUID_TO_STEPPING macro and converted existing code to use it.
Reviewed by: mav MFC after: 2 weeks Sponsored by: iXsystems, Inc. Differential Revision: https://reviews.freebsd.org/D25673
show more ...
|
|
Revision tags: release/11.4.0 |
|
| #
7029da5c |
| 26-Feb-2020 |
Pawel Biernacki <[email protected]> |
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many)
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly mark
Mark more nodes as CTLFLAG_MPSAFE or CTLFLAG_NEEDGIANT (17 of many)
r357614 added CTLFLAG_NEEDGIANT to make it easier to find nodes that are still not MPSAFE (or already are but aren’t properly marked). Use it in preparation for a general review of all nodes.
This is non-functional change that adds annotations to SYSCTL_NODE and SYSCTL_PROC nodes using one of the soon-to-be-required flags.
Mark all obvious cases as MPSAFE. All entries that haven't been marked as MPSAFE before are by default marked as NEEDGIANT
Approved by: kib (mentor, blanket) Commented by: kib, gallatin, melifaro Differential Revision: https://reviews.freebsd.org/D23718
show more ...
|
|
Revision tags: release/12.1.0, release/11.3.0 |
|
| #
e2e050c8 |
| 20-May-2019 |
Conrad Meyer <[email protected]> |
Extract eventfilter declarations to sys/_eventfilter.h
This allows replacing "sys/eventfilter.h" includes with "sys/_eventfilter.h" in other header files (e.g., sys/{bus,conf,cpu}.h) and reduces hea
Extract eventfilter declarations to sys/_eventfilter.h
This allows replacing "sys/eventfilter.h" includes with "sys/_eventfilter.h" in other header files (e.g., sys/{bus,conf,cpu}.h) and reduces header pollution substantially.
EVENTHANDLER_DECLARE and EVENTHANDLER_LIST_DECLAREs were moved out of .c files into appropriate headers (e.g., sys/proc.h, powernv/opal.h).
As a side effect of reduced header pollution, many .c files and headers no longer contain needed definitions. The remainder of the patch addresses adding appropriate includes to fix those files.
LOCK_DEBUG and LOCK_FILE_LINE_ARG are moved to sys/_lock.h, as required by sys/mutex.h since r326106 (but silently protected by header pollution prior to this change).
No functional change (intended). Of course, any out of tree modules that relied on header pollution for sys/eventhandler.h, sys/lock.h, or sys/mutex.h inclusion need to be fixed. __FreeBSD_version has been bumped.
show more ...
|
|
Revision tags: release/12.0.0, release/11.2.0 |
|
| #
2e3f84e5 |
| 15-Jun-2018 |
Matt Macy <[email protected]> |
Quiet coretemp probe
Only the first device will print coretemp0: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu0 instead of all hyper threads
Submitted by: kbowling Reviewed by: imp, sbruno Spon
Quiet coretemp probe
Only the first device will print coretemp0: <CPU On-Die Thermal Sensors> numa-domain 0 on cpu0 instead of all hyper threads
Submitted by: kbowling Reviewed by: imp, sbruno Sponsored by: Limelight Networks Differential Revision: https://reviews.freebsd.org/D15727
show more ...
|
| #
718cf2cc |
| 27-Nov-2017 |
Pedro F. Giffuni <[email protected]> |
sys/dev: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error
sys/dev: further adoption of SPDX licensing ID tags.
Mainly focus on files that use BSD 2-Clause license, however the tool I was using misidentified many licenses so this was mostly a manual - error prone - task.
The Software Package Data Exchange (SPDX) group provides a specification to make it easier for automated tools to detect and summarize well known opensource licenses. We are gradually adopting the specification, noting that the tags are considered only advisory and do not, in any way, superceed or replace the license texts.
show more ...
|
|
Revision tags: release/10.4.0, release/11.1.0, release/11.0.1, release/11.0.0 |
|
| #
9d6672e1 |
| 22-May-2016 |
Luiz Otavio O Souza <[email protected]> |
Fix the deciKelvin to Celsius conversion in kernel.
After r285994, sysctl(8) was fixed to use 273.15 instead of 273.20 as 0C reference and as result, the temperature read in sysctl(8) now exibits a
Fix the deciKelvin to Celsius conversion in kernel.
After r285994, sysctl(8) was fixed to use 273.15 instead of 273.20 as 0C reference and as result, the temperature read in sysctl(8) now exibits a +0.1C difference.
This commit fix the kernel references to match the reference value used in sysctl(8) after r285994.
Sponsored by: Rubicon Communications (Netgate)
show more ...
|
|
Revision tags: release/10.3.0, release/10.2.0, release/10.1.0, release/9.3.0, release/10.0.0, release/9.2.0, release/8.4.0 |
|
| #
e42412a9 |
| 18-Feb-2013 |
Mark Johnston <[email protected]> |
Mark the coretemp(4) sysctls as MPSAFE, ensuring that Giant won't be held unnecessarily by a user thread waiting to run on a specific CPU after calling sched_bind().
Reviewed by: rstone Approved by:
Mark the coretemp(4) sysctls as MPSAFE, ensuring that Giant won't be held unnecessarily by a user thread waiting to run on a specific CPU after calling sched_bind().
Reviewed by: rstone Approved by: emaste (co-mentor) Sponsored by: Sandvine Incorporated MFC after: 1 week
show more ...
|
| #
61bfd867 |
| 30-Jan-2013 |
Sofian Brabez <[email protected]> |
Use DEVMETHOD_END macro defined in sys/bus.h instead of {0, 0} sentinel on device_method_t arrays
Reviewed by: cognet Approved by: cognet
|
|
Revision tags: release/9.1.0 |
|
| #
a8de37b0 |
| 22-Oct-2012 |
Eitan Adler <[email protected]> |
This isn't functionally identical. In some cases a hint to disable unit 0 would in fact disable all units.
This reverts r241856
Approved by: cperciva (implicit)
|
| #
76b75122 |
| 22-Oct-2012 |
Eitan Adler <[email protected]> |
Now that device disabling is generic, remove extraneous code from the device drivers that used to provide this feature.
Reviewed by: des Approved by: cperciva MFC after: 1 week
|
|
Revision tags: release/8.3.0_cvs, release/8.3.0, release/9.0.0 |
|
| #
c839b5bb |
| 19-Sep-2011 |
Attilio Rao <[email protected]> |
#PROCHOT assertion is sticky after reading the MSR (accordingly with Intel manuals) it must be cleared by writing a 0. Fix that.
Sponsored by: Sandvine Incorporated Reported by: rstone Reviewed by:
#PROCHOT assertion is sticky after reading the MSR (accordingly with Intel manuals) it must be cleared by writing a 0. Fix that.
Sponsored by: Sandvine Incorporated Reported by: rstone Reviewed by: delphij, emaste, rstone Approved by: re (kib) MFC after: 1 week
show more ...
|
| #
d1f97f76 |
| 02-Sep-2011 |
Xin LI <[email protected]> |
Expose more variables from coretemp(4) via sysctl:
- tjmax - Tj(max) value from the CPU - delta - current delta reading - resolution - sensor resolution in Celsius - throttle_log - whether a #PR
Expose more variables from coretemp(4) via sysctl:
- tjmax - Tj(max) value from the CPU - delta - current delta reading - resolution - sensor resolution in Celsius - throttle_log - whether a #PROCHOT was asserted since last reset
Submitted by: Mark Johnston <markjdb gmail.com> (mostly) MFC after: 1 month Approved by: re (kib)
show more ...
|
| #
72dc07eb |
| 19-Aug-2011 |
Attilio Rao <[email protected]> |
Bump the maximum coretemp limit (for CPU temperature) to 110. Several cores with temp in the range 101-105 have been found in the past.
Sponsored by: Sandvine Incorporated Reviewed by: delphij, emas
Bump the maximum coretemp limit (for CPU temperature) to 110. Several cores with temp in the range 101-105 have been found in the past.
Sponsored by: Sandvine Incorporated Reviewed by: delphij, emaste Approved by: re (kib) MFC after: 3 days
show more ...
|
| #
89017932 |
| 05-May-2011 |
Xin LI <[email protected]> |
Detect and set Atom's Tj(max) to 90 if it's not the 45nm D400/D500/N400 series.
MFC after: 2 weeks
|
| #
ba95b1e1 |
| 02-May-2011 |
Xin LI <[email protected]> |
Correct a typo. According to Intel document 318914, the Tj(max) for Core 2 Duo Mobile CPUs should be 105.
Noticed by: Mark Johnston <markjdb gmail.com> MFC after: 3 days
|
|
Revision tags: release/7.4.0_cvs, release/8.2.0_cvs, release/7.4.0, release/8.2.0 |
|
| #
28a54cac |
| 04-Aug-2010 |
Xin LI <[email protected]> |
Catch known CPUs before using IA32_TEMPERATURE_TARGET. This way we would have an opportunity to hide the Tj(target) value doesn't seem right stuff if we know it's not working there.
Add temperature
Catch known CPUs before using IA32_TEMPERATURE_TARGET. This way we would have an opportunity to hide the Tj(target) value doesn't seem right stuff if we know it's not working there.
Add temperature value for Core2 Duo Extreme Mobile that I have access to.
show more ...
|
| #
a3bc0a4e |
| 29-Jul-2010 |
Xin LI <[email protected]> |
Improve cputemp(4) driver wrt newer Intel processors, especially Xeon 5500/5600 series:
- Utilize IA32_TEMPERATURE_TARGET, a.k.a. Tj(target) in place of Tj(max) when a sane value is available, a
Improve cputemp(4) driver wrt newer Intel processors, especially Xeon 5500/5600 series:
- Utilize IA32_TEMPERATURE_TARGET, a.k.a. Tj(target) in place of Tj(max) when a sane value is available, as documented in Intel whitepaper "CPU Monitoring With DTS/PECI"; (By sane value we mean 70C - 100C for now); - Print the probe results when booting verbose; - Replace cpu_mask with cpu_stepping; - Use CPUID_* macros instead of rolling our own.
Approved by: rpaulo MFC after: 1 month
show more ...
|
|
Revision tags: release/8.1.0_cvs, release/8.1.0, release/7.3.0_cvs, release/7.3.0, release/8.0.0_cvs, release/8.0.0 |
|
| #
87c120a6 |
| 13-Sep-2009 |
Norikatsu Shigemura <[email protected]> |
MFC r196889: Change 'dev.cpu.N.temperature', sysctl I (degC) to IK (Kelvin), to match acpi_thermal(4) and amdtemp(4).
Approved by: re (rwatson) Reviewed by: rpaulo Suggested by: ume
|