mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ALOK TIWARI <alok.a.tiwari@oracle.com>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	hdegoede@redhat.com, ilpo.jarvinen@linux.intel.com
Cc: platform-driver-x86@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 5/5] Documentation: admin-guide: pm: Add documentation for die_id
Date: Wed, 23 Apr 2025 14:40:40 +0530	[thread overview]
Message-ID: <7b09613c-2aba-469f-bc33-358b787e29b0@oracle.com> (raw)
In-Reply-To: <20250422213427.1943328-6-srinivas.pandruvada@linux.intel.com>



On 23-04-2025 03:04, Srinivas Pandruvada wrote:
> +``die_id``
> +	This attribute is used to get the Linux die id of this instance.
> +	This attributes is only present for domains with core agents and

typo attributes ->attribute

> +        when the CPUID leaf 0x1f presents die ID.
> +
>   ``fabric_cluster_id``
>   	This attribute is used to get the fabric cluster id of this instance.
>   


Thanks,
Alok

  reply	other threads:[~2025-04-23  9:10 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-22 21:34 [PATCH 0/5] intel-uncore-freq: Add agent_types and die_id attributes Srinivas Pandruvada
2025-04-22 21:34 ` [PATCH 1/5] platform/x86/intel-uncore-freq: Add attributes to show agent types Srinivas Pandruvada
2025-04-22 21:34 ` [PATCH 2/5] Documentation: admin-guide: pm: Add documentation for agent_types Srinivas Pandruvada
2025-04-22 21:34 ` [PATCH 3/5] platform/x86/intel: power-domains: Add interface to get Linux die ID Srinivas Pandruvada
2025-04-22 21:34 ` [PATCH 4/5] platform/x86/intel-uncore-freq: Add attributes to show die_id Srinivas Pandruvada
2025-04-22 21:34 ` [PATCH 5/5] Documentation: admin-guide: pm: Add documentation for die_id Srinivas Pandruvada
2025-04-23  9:10   ` ALOK TIWARI [this message]
2025-04-23 13:52     ` srinivas pandruvada

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=7b09613c-2aba-469f-bc33-358b787e29b0@oracle.com \
    --to=alok.a.tiwari@oracle.com \
    --cc=hdegoede@redhat.com \
    --cc=ilpo.jarvinen@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®