Linux Power Management development
 help / color / mirror / Atom feed
From: Changwoo Min <changwoo@igalia.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>,
	Lukasz Luba <lukasz.luba@arm.com>
Cc: christian.loehle@arm.com, tj@kernel.org, pavel@kernel.org,
	kernel-dev@igalia.com, linux-pm@vger.kernel.org,
	linux-kernel@vger.kernel.org, len.brown@intel.com
Subject: Re: [PATCH v2] PM: EM: Add inotify support when the energy model is updated.
Date: Sat, 10 May 2025 14:07:45 +0900	[thread overview]
Message-ID: <90834b07-9261-4be6-a10b-88d3f5308e1e@igalia.com> (raw)
In-Reply-To: <CAJZ5v0ixh=ra-TDbC59rpZoGn0pRWmAMchHqoOb_XwB2XUzA7Q@mail.gmail.com>

Thank you, Rafael, for the pointer.

On 5/10/25 01:41, Rafael J. Wysocki wrote:
>>
>> I have discussed that with Rafael and we have similar view.
>> The EM debugfs is not the right interface for this purpose.
>>
>> A better design and mechanism for your purpose would be the netlink
>> notification. It is present in the kernel in thermal framework
>> and e.g. is used by Intel HFI
>> - drivers/thermal/intel/intel_hfi.c
>> - drivers/thermal/thermal_netlink.c
>> It's able to send to the user space the information from FW about
>> the CPUs' efficiency changes, which is similar to this EM modification.
> 
> In addition, after this patch
> 
> https://lore.kernel.org/linux-pm/3637203.iIbC2pHGDl@rjwysocki.net/
> 
> which is about to get into linux-next, em_dev_update_perf_domain()
> will not be the only place where the Energy Model can be updated.

I am curious about whether the energy mode is likely to be updated more
often with this change. How often the energy model is likely to be
updated is the factor to be considered for the interface and the model
to post-processing the eneergy model (in the BPF schedulers).

Regards,
Changwoo Min

> 
> Thanks!
> _______________________________________________
> Kernel-dev mailing list -- kernel-dev@igalia.com
> To unsubscribe send an email to kernel-dev-leave@igalia.com


  reply	other threads:[~2025-05-10  5:08 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  1:47 [PATCH v2] PM: EM: Add inotify support when the energy model is updated Changwoo Min
2025-05-07 17:04 ` Tejun Heo
2025-05-08  6:03   ` Changwoo Min
2025-05-09 10:55 ` Lukasz Luba
2025-05-09 16:41   ` Rafael J. Wysocki
2025-05-10  5:07     ` Changwoo Min [this message]
2025-05-10 11:34       ` Rafael J. Wysocki
2025-05-22  8:19         ` Lukasz Luba
2025-05-22  8:35           ` Changwoo Min
2025-05-22  8:43             ` Lukasz Luba
2025-05-10  4:40   ` Changwoo Min

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=90834b07-9261-4be6-a10b-88d3f5308e1e@igalia.com \
    --to=changwoo@igalia.com \
    --cc=christian.loehle@arm.com \
    --cc=kernel-dev@igalia.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=pavel@kernel.org \
    --cc=rafael@kernel.org \
    --cc=tj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox