From: Rudolf Marek <r.marek@assembler.cz>
To: lm-sensors@vger.kernel.org
Subject: Re: [lm-sensors] New field in MSR_TEMPERATURE_TARGET
Date: Sat, 03 May 2014 20:32:49 +0000 [thread overview]
Message-ID: <53655271.7080505@assembler.cz> (raw)
In-Reply-To: <20140501120744.1cddd118@endymion.delvare>
Hi Khali,
After some google magic I found this:
http://www.intel.com/content/dam/www/public/us/en/documents/datasheets/4th-gen-core-family-mobile-u-y-processor-lines-vol-1-datasheet.pdf
TCC Activation Offset can be used to activate the Adaptive Thermal Monitor at
temperatures lower than TjMAX. It is the preferred thermal protection mechanism
for Intel Turbo Boost Technology 2.0 operation since ACPI passive throttling
states will pull the processor out of turbo mode operation when triggered. An
offset (in degrees Celsius) can be written to the TEMPERATURE_TARGET (0x1A2)
MSR, bits [29:24]. This value will be subtracted from the value found in bits
[23:16]. The default offset is 0 °C, where throttling will occur at TjMAX. The
offset should be set lower than any other protection such as ACPI _PSV trip points.
So yes you could make it writable by user, and this value is always subtracted.
It looks like this should be taken into account for tempN_crit on the Silvermont
CPUs.
The Silvermont CPU can be identified in your [1] by looking at 35.4:
Table 35-6 lists model-specific registers (MSRs) for Intel processors based on
the Silvermont microarchitecture These processors have a CPUID signature with
DisplayFamily_DisplayModel of 06_37H, 06_4AH, 06_4DH,
06_5AH, and 06_5DH, see Table 35-1.
Thanks
Rudolf
_______________________________________________
lm-sensors mailing list
lm-sensors@lm-sensors.org
http://lists.lm-sensors.org/mailman/listinfo/lm-sensors
prev parent reply other threads:[~2014-05-03 20:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-01 10:07 [lm-sensors] New field in MSR_TEMPERATURE_TARGET Jean Delvare
2014-05-01 11:16 ` Guenter Roeck
2014-05-03 20:32 ` Rudolf Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=53655271.7080505@assembler.cz \
--to=r.marek@assembler.cz \
--cc=lm-sensors@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.