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: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Subject: Re: [Xen-devel] CPU frequency throttling based on the temperature
Date: Wed, 24 Jul 2019 14:47:19 +0000	[thread overview]
Message-ID: <1f653322-5d4d-5393-5790-c63b07492050@suse.com> (raw)
In-Reply-To: <20190724143643.lpg576p6psxqelrg@Air-de-Roger>

On 24.07.2019 16:36, Roger Pau Monné  wrote:
> On Wed, Jul 24, 2019 at 10:01:40AM -0400, Fredy P. wrote:
>> My objective is to get CPU frequency throttling based on the
>> temperature in a Xen/OpenWRT(dom0) system.
>>
>> After to expend hours reading Xen's wiki, mailing list archives,
>> commits, googling and asking in the IRC channel I'm coming here asking
>> for help because I hope there is something I miss and you could point
>> it.
> 
> That seems like an interesting project, I guess your focus is some
> kind of low-power device? (not that it matters much for the context of
> the question).
> 
> Anyway, thanks for your interest on Xen and ways to improve it!
> 
>> My first question is, there is any way to do CPU frequency throttling
>> based on the temperature?
> 
> I don't think there's such governor ATM implemented in Xen, the more
> that I think all frequency throttling is supposed to be done by dom0
> using xenpm, but not Xen itself?

The original authors of P- and C-state handling look to have
assumed that T-state handling should work similarly, i.e. by
Dom0 uploading relevant data. See public/platform.h starting at

#define XENPF_set_processor_pminfo      54

where in particular you'll find

#define XEN_PM_TX   2

Additionally "done by dom0 using xenpm" still means Xen carrying
out the actual operation. And xenpm of course is only an
auxiliary tool by which an admin can influence overall behavior,
it doesn't replace a proper governor.

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

  reply	other threads:[~2019-07-24 14:56 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 [this message]
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
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=1f653322-5d4d-5393-5790-c63b07492050@suse.com \
    --to=jbeulich@suse.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.