Linux ACPI
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: James Morse <james.morse@arm.com>
Cc: <linux-acpi@vger.kernel.org>, Rafael Wysocki <rafael@kernel.org>,
	Len Brown <lenb@kernel.org>, <jeremy.linton@arm.com>,
	Rohit Mathew <Rohit.Mathew@arm.com>
Subject: Re: [PATCH 4/4] ACPI / PPTT: Add a helper to fill a cpumask from a cache_id
Date: Mon, 23 Jun 2025 14:22:59 +0100	[thread overview]
Message-ID: <20250623-witty-exotic-poodle-3fe0cf@sudeepholla> (raw)
In-Reply-To: <20250612171336.4858-5-james.morse@arm.com>

On Thu, Jun 12, 2025 at 05:13:36PM +0000, James Morse wrote:
> MPAM identifies CPUs by the cache_id in the PPTT cache structure.
> 
> The driver needs to know which CPUs are associated with the cache,
> the CPUs may not all be online, so cacheinfo does not have the
> information.
> 
> Add a helper to pull this information out of the PPTT.
>

Reviewed-by: Sudeep Holla <sudeep.holla@arm.com>

-- 
Regards,
Sudeep

      reply	other threads:[~2025-06-23 13:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-12 17:13 [PATCH 0/4] ACPI / PPTT: Add helpers to fill cpumask from PPTT James Morse
2025-06-12 17:13 ` [PATCH 1/4] ACPI / PPTT: Add a helper to fill a cpumask from a processor container James Morse
2025-06-23 13:08   ` Sudeep Holla
2025-06-26 17:14     ` James Morse
2025-06-23 13:21   ` Sudeep Holla
2025-06-26 17:11     ` James Morse
2025-06-26 17:10   ` James Morse
2025-06-12 17:13 ` [PATCH 2/4] ACPI / PPTT: Stop acpi_count_levels() expecting callers to clear levels James Morse
2025-06-23 13:10   ` Sudeep Holla
2025-06-26 17:11     ` James Morse
2025-06-12 17:13 ` [PATCH 3/4] ACPI / PPTT: Find cache level by cache-id James Morse
2025-06-23 13:21   ` Sudeep Holla
2025-06-12 17:13 ` [PATCH 4/4] ACPI / PPTT: Add a helper to fill a cpumask from a cache_id James Morse
2025-06-23 13:22   ` Sudeep Holla [this message]

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=20250623-witty-exotic-poodle-3fe0cf@sudeepholla \
    --to=sudeep.holla@arm.com \
    --cc=Rohit.Mathew@arm.com \
    --cc=james.morse@arm.com \
    --cc=jeremy.linton@arm.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=rafael@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