| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
device_method_t arrays
Reviewed by: cognet
Approved by: cognet
|
|
|
|
|
|
|
|
| |
unit 0 would in fact disable all units.
This reverts r241856
Approved by: cperciva (implicit)
|
|
|
|
|
|
|
|
| |
device drivers that used to provide this feature.
Reviewed by: des
Approved by: cperciva
MFC after: 1 week
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
|
|
|
|
| |
- 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)
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
| |
series.
MFC after: 2 weeks
|
|
|
|
|
|
|
| |
Duo Mobile CPUs should be 105.
Noticed by: Mark Johnston <markjdb gmail.com>
MFC after: 3 days
|
|
|
|
|
|
|
|
|
| |
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.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
Approved by: re (rwatson)
Reviewed by: rpaulo
Suggested by: ume
MFC After: 3 days
|
|
|
|
| |
Reviewed by: jhb, peter (early amd64 version)
|
|
|
|
| |
MFC after: 1 day
|
|
|
|
|
|
| |
Submitted by: Arthur Hartwig <arthur.hartwig at nokia.com>
PR: 122878
MFC after: 3 days
|
|
|
|
|
|
|
| |
querying the number of sensors returns > 0.
PR: 120541
Approved by: njl (mentor)
|
|
|
|
|
|
| |
no problem with coretemp and C3 state.
Approved by: njl (mentor)
|
|
|
|
|
| |
Requested by: phk
Discussed on: cvs-all
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
|
|
| |
critical temperature + sched_unbind() after rdmsr + initialize sc_dev.
Submitted by: Rui Paulo <rpaulo@fnop.net>, cnst
Approved by: re (kensmith)
|
|
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
|