Linux Power Management development
 help / color / mirror / Atom feed
From: srinivas pandruvada <srinivas.pandruvada@linux.intel.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Linux PM <linux-pm@vger.kernel.org>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
	Daniel Lezcano <daniel.lezcano@linaro.org>,
	"Zhang, Rui" <rui.zhang@intel.com>,
	Lukasz Luba <lukasz.luba@arm.com>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Morten Rasmussen <morten.rasmussen@arm.com>,
	Ulf Hansson <ulf.hansson@linaro.org>,
	Mario Limonciello <mario.limonciello@amd.com>
Subject: Re: [CfP] Power Management and Thermal Control MC (LPC2023)
Date: Mon, 22 May 2023 15:33:51 -0700	[thread overview]
Message-ID: <abcc6689c283bbe91b6fd16572cfd4a8d5e78cc6.camel@linux.intel.com> (raw)
In-Reply-To: <CAJZ5v0juUuy2xKZHMXAKSRtfQxMyL6z12AFdU8_ZbdFRKKrR=Q@mail.gmail.com>

Hi Rafael,

On Mon, 2023-05-22 at 19:12 +0200, Rafael J. Wysocki wrote:
> Hi Folks,
> 
> I'm going to submit a Power Management and Thermal Control
> micro-conference proposal for LPC2023 along the lines of what
> happened
> in the previous iterations of it.
> 
> If you have topics that you'd like to be discussed there, please let
> me know by Friday, May 26.
> 
> Please note that LPC MC topics are expected to cover work in progress
> or at the concept stage.  They are not  supposed to be about work
> that
> has been done already.
"
1.
Idle injection and soft IRQs:
We still have no good solution to avoid races with soft IRQ scheduling
while using idle injection. The previous post to kernel to solve this
issue is rejected. Peter proposed a change, that also didn't work.

I am proposing a discussion on how the solve this:
- May be we need to use some in kernel IRQ affinity change for the
forced idle CPUs
- Other potential solution?

"

2.
Thermal sysfs/API Update

Thermal sysfs v2
There was proposal to correctly abstract thermal zones, sensors,
cooling devices and policies. Are we happy with the current state?

- Add capability to define additional private attributes for a zone
like cpufreq

Thanks,
Srinivas

> 
> Kind regards,
> Rafael


  parent reply	other threads:[~2023-05-22 22:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 17:12 [CfP] Power Management and Thermal Control MC (LPC2023) Rafael J. Wysocki
2023-05-22 17:52 ` Lukasz Luba
2023-05-22 18:18   ` Rafael J. Wysocki
2023-05-22 22:33 ` srinivas pandruvada [this message]
2023-05-23 10:51   ` Rafael J. Wysocki
2023-05-24  1:53 ` Zhang, Rui
2023-05-24  8:06 ` Daniel Lezcano
2023-05-24 10:25   ` Rafael J. Wysocki
2023-05-24 11:50     ` Daniel Lezcano
2023-05-25  9:18 ` Sudeep Holla
2023-05-31 10:16 ` Morten Rasmussen
2023-05-31 11:07   ` Vincent Guittot
2023-05-31 12:00     ` Steven Rostedt
2023-05-31 12:50       ` Steven Rostedt
2023-05-31 12:09     ` Morten Rasmussen
2023-05-31 12:31       ` Vincent Guittot
2023-05-31 15:16   ` Rafael J. Wysocki
2023-05-31 10:36 ` Ulf Hansson
2023-07-19 17:15 ` Rafael J. Wysocki
2023-08-22 20:32   ` Rafael J. Wysocki

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=abcc6689c283bbe91b6fd16572cfd4a8d5e78cc6.camel@linux.intel.com \
    --to=srinivas.pandruvada@linux.intel.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=mario.limonciello@amd.com \
    --cc=morten.rasmussen@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    --cc=sudeep.holla@arm.com \
    --cc=ulf.hansson@linaro.org \
    --cc=viresh.kumar@linaro.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox