All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Gwara, Mateusz" <mateusz.gwara@secunet.com>
To: "rafael@kernel.org" <rafael@kernel.org>,
	"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
	"rui.zhang@intel.com" <rui.zhang@intel.com>,
	"lukasz.luba@arm.com" <lukasz.luba@arm.com>
Cc: "linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
	"Wassenberg, Dennis" <Dennis.Wassenberg@secunet.com>
Subject: TCC cooling on Meteorlake
Date: Mon, 24 Feb 2025 11:27:22 +0000	[thread overview]
Message-ID: <163ff391dc6d4f828ecff95e87f5003d@secunet.com> (raw)
In-Reply-To: <f733005155e64d489ae18d7d357bada9@secunet.com>

Hi,

Sorry, my first mail was sent as HTML due to a corporate policy preset.
So here's my initial mail:


Hello dear maintainers!

I was comparing the behavior of the Intel TCC cooling driver on a kernel we develop and also on regular Ubuntu kernel releases(based on Linux kernel up to 6.13).
On a Raptorlake CPU you’ll see the TCC node with e.g.:

/sys/class/thermal/cooling_device8/type
/sys/class/thermal/cooling_device8/cur_state

Endpoints

This allows reading/setting the offsets as expected.

This was made possible in
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers?h=next-20250212&id=be6bfb29c55e48567983e24aba7b6bf9a66a45ab/https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal?h=next-20250212&id=be6bfb29c55e48567983e24aba7b6bf9a66a45ab/https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal/intel?h=next-20250212&id=be6bfb29c55e48567983e24aba7b6bf9a66a45ab/https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/commit/drivers/thermal/intel/intel_tcc_cooling.c?h=next-20250212&id=be6bfb29c55e48567983e24aba7b6bf9a66a45ab

with a patch that added 
> +       X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE,           &temp_tigerlake),
> +       X86_MATCH_INTEL_FAM6_MODEL(ALDERLAKE_L,         &temp_tigerlake),
> +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE,          &temp_tigerlake),
> +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_P,        &temp_tigerlake),
> +       X86_MATCH_INTEL_FAM6_MODEL(RAPTORLAKE_S,        &temp_tigerlake),

Among other changes, where intel_tcc_get_offset_mask would get the correct Tjunction offset for each CPU.

I was trying to add a similar entry corresponding to the Meteorlake Model names but this did not have the same effect and there was no TCC node present like on a Raptorlake device.
                
As I see in
https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git/tree/drivers/thermal/intel/intel_tcc_cooling.c?h=next-20250219
the last CPU added here still is the Raptorlake model.

I checked the repositories where Intel maintains their CPU patches but there was also no mention of Meteorlake (and later models)regarding TCC support.
As there have been several ARROW&LUNAR-lake patches handling different issues regarding clocking the different core variants.

I’d like to know if there is something I’m missing(maybe NO TCC support since Meteorlake?) or if there is TCC support planned?
I’d be willing to help test anything regarding this issue.


Sorry for the lengthy mail and thank you for you work on the Linux Kernel so far :)



Mateusz 


-- 
Mateusz Gwara
Senior Software Developer
Department Network & Client Security
Division Public Authorities
secunet Security Networks AG

Tel.: +49 201 54 54-2934
E-Mail: mailto:mateusz.gwara@secunet.com
Alt-Moabit 96, 10559 Berlin
http://www.secunet.com
______________________________________________________________________

secunet Security Networks AG
Sitz: Kurfürstenstraße 58, 45138 Essen, Deutschland
Amtsgericht Essen HRB 13615
Vorstand: Axel Deininger (Vors.), Torsten Henn, Dr. Kai Martius, Jessica Nospers
Aufsichtsratsvorsitzender: Dr. Ralf Wintergerst
______________________________________________________________________


       reply	other threads:[~2025-02-24 11:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f733005155e64d489ae18d7d357bada9@secunet.com>
2025-02-24 11:27 ` Gwara, Mateusz [this message]
2025-03-11 12:19 TCC cooling on Meteorlake Gwara, Mateusz
2025-03-13  5:29 ` Zhang, Rui
  -- strict thread matches above, loose matches on Subject: below --
2025-03-17 10:31 Gwara, Mateusz
2025-03-24  0:17 ` Zhang, Rui
2025-03-26 17:46 Gwara, Mateusz

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=163ff391dc6d4f828ecff95e87f5003d@secunet.com \
    --to=mateusz.gwara@secunet.com \
    --cc=Dennis.Wassenberg@secunet.com \
    --cc=daniel.lezcano@linaro.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=lukasz.luba@arm.com \
    --cc=rafael@kernel.org \
    --cc=rui.zhang@intel.com \
    /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.