| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
|
| |
Cleanup #PROCHOT sticky assertion.
Sponsored by: Sandvine Incorporated
Notes:
svn path=/stable/8/; revision=225933
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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)
Notes:
svn path=/stable/8/; revision=225916
|
| |
|
|
|
|
|
|
|
| |
Bump coretemp tollerable limit to 110 degrees.
Sponsored by: Sandvine Incorporated
Notes:
svn path=/stable/8/; revision=225105
|
| |
|
|
|
|
|
|
| |
Detect and set Atom's Tj(max) to 90 if it's not the 45nm D400/D500/N400
series.
Notes:
svn path=/stable/8/; revision=222101
|
| |
|
|
|
|
|
|
|
|
| |
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>
Notes:
svn path=/stable/8/; revision=221493
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
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.
Notes:
svn path=/stable/8/; revision=211914
|
| |
|
|
|
|
|
|
|
|
|
|
| |
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
Notes:
svn path=/stable/8/; revision=197149
|
| |
|
|
|
|
|
| |
Reviewed by: jhb, peter (early amd64 version)
Notes:
svn path=/head/; revision=185341
|
| |
|
|
|
|
|
| |
MFC after: 1 day
Notes:
svn path=/head/; revision=178989
|
| |
|
|
|
|
|
|
|
| |
Submitted by: Arthur Hartwig <arthur.hartwig at nokia.com>
PR: 122878
MFC after: 3 days
Notes:
svn path=/head/; revision=178950
|
| |
|
|
|
|
|
|
|
|
| |
querying the number of sensors returns > 0.
PR: 120541
Approved by: njl (mentor)
Notes:
svn path=/head/; revision=176279
|
| |
|
|
|
|
|
|
|
| |
no problem with coretemp and C3 state.
Approved by: njl (mentor)
Notes:
svn path=/head/; revision=175214
|
| |
|
|
|
|
|
|
| |
Requested by: phk
Discussed on: cvs-all
Notes:
svn path=/head/; revision=172674
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
make sure to never call sched_bind() for uninitialised CPUs.
Submitted by: Constantine A. Murenin <cnst@FreeBSD.org>
Sponsored by: Google Summer of Code 2007 (GSoC2007/cnst-sensors)
Mentored by: syrinx
Tested by: many
OKed by: kensmith
Notes:
svn path=/head/; revision=172633
|
| |
|
|
|
|
|
|
|
|
| |
critical temperature + sched_unbind() after rdmsr + initialize sc_dev.
Submitted by: Rui Paulo <rpaulo@fnop.net>, cnst
Approved by: re (kensmith)
Notes:
svn path=/head/; revision=171933
|
|
|
and newer CPUs (including Core 2 and Core / Core 2 based Xeons). The
driver attaches to each cpu device and creates a sysctl node in that
device's sysctl context (dev.cpu.N.temperature). When invoked, the
handler binds to the appropriate CPU to ensure a correct reading.
Submitted by: Rui Paulo <rpaulo@fnop.net>
Sponsored by: Google Summer of Code 2007
Tested by: des, marcus, Constantine A. Murenin, Ian FREISLICH
Approved by: re (kensmith)
MFC after: 3 weeks
Notes:
svn path=/head/; revision=171854
|