All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <JBeulich@suse.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>,
	"Fredy P." <fredy.pulido@savoirfairelinux.com>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
	"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] CPU frequency throttling based on the temperature
Date: Thu, 25 Jul 2019 13:59:22 +0000	[thread overview]
Message-ID: <0f520921-51a5-22c3-bd5d-7774f26bac30@suse.com> (raw)
In-Reply-To: <20190725134750.d5hw6dsxjowk4ann@Air-de-Roger>

On 25.07.2019 15:47, Roger Pau Monné  wrote:
> On Thu, Jul 25, 2019 at 09:29:01AM -0400, Fredy P. wrote:
>> On Thu, 2019-07-25 at 15:13 +0200, Roger Pau Monné wrote:
>>> On Thu, Jul 25, 2019 at 12:54:46PM +0000, Jan Beulich wrote:
>>>> On 25.07.2019 14:44,  Fredy P.  wrote:
>>>>> On Wed, 2019-07-24 at 17:41 +0200, Roger Pau Monné wrote:
>>>>>>>> What hardware interface does thermald (or the driver in
>>>>>>>> Linux if
>>>>>>>> there's one) use to get the temperature data?
>>>>>
>>>>> In our initial POC using Xen 4.8.x we where using Linux coretemp
>>>>> driver
>>>>> reading by example /class/sys/hwmon/hwmon0/temp3_input but it got
>>>>> deprecated at commit 72e038450d3d5de1a39f0cfa2d2b0f9b3d43c6c6
>>>>
>>>> Hmm, I wouldn't call this deprecation, but a regression. I would
>>>> say we want to re-expose this leaf to Dom0, the more that the
>>>> commit also only mentions unprivileged domains. Andrew?
>>>
>>> AFAICT from the documents provided by Fredy the temperature is read
>>> from a MSR that reports the current temperature of the core on which
>>> the MSR is read from. When running on Xen this will only work
>>> correctly if dom0 is given the same vCPUs as pCPUs and those are
>>> identity pinned.
>>
>> I just want to be sure I got it correctly, by saying "When running on
>> Xen this will only work correctly if ..." means in a future
>> implementation or that right now could work if I pin this v/pCPUS?
> 
> No, right now there's no way to get this data from dom0, regardless of
> the pinning.

Of course you can, using the MSR "device" Linux optionally
provides (plus perhaps the rdmsr utility from the msr-tools
package).

> The commit you mention simply removes exposing the feature on CPUID,
> but I'm not sure whether access to the actual MSR is also forbidden. I
> think so since we do MSR white listing IIRC, and I don't seem to find
> MSR_IA32_THERM_STATUS white listed anywhere.

At least for PV we continue to let everything not specially
handled shine through - see the bottom of pv/emul-pro-op.c:read_msr().

Jan
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2019-07-25 14:06 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-24 14:01 [Xen-devel] CPU frequency throttling based on the temperature Fredy P.
2019-07-24 14:36 ` Roger Pau Monné
2019-07-24 14:47   ` Jan Beulich
2019-07-24 15:35     ` Roger Pau Monné
2019-07-24 15:51       ` Jan Beulich
2019-07-24 17:10       ` Fredy P.
2019-07-24 15:25   ` Fredy P.
2019-07-24 15:41     ` Roger Pau Monné
2019-07-25 12:44       ` Fredy P.
2019-07-25 12:54         ` Jan Beulich
2019-07-25 13:07           ` Fredy P.
2019-07-25 13:13           ` Roger Pau Monné
2019-07-25 13:29             ` Fredy P.
2019-07-25 13:47               ` Roger Pau Monné
2019-07-25 13:59                 ` Jan Beulich [this message]
2019-07-25 14:17                   ` Roger Pau Monné
2019-07-25 14:31                     ` Jan Beulich
2019-07-25 15:34                       ` Roger Pau Monné
2019-07-25 16:29                         ` Fredy P.
2019-07-25 13:43             ` Jan Beulich
2019-07-25 14:07               ` Roger Pau Monné
2019-07-25 14:27                 ` Fredy P.

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=0f520921-51a5-22c3-bd5d-7774f26bac30@suse.com \
    --to=jbeulich@suse.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=fredy.pulido@savoirfairelinux.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.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.