LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Machhiwal <amachhiw@linux.ibm.com>
To: Mahesh Salgaonkar <mahesh@linux.ibm.com>
Cc: linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	Madhavan Srinivasan <maddy@linux.ibm.com>,
	Praveen K Pandey <praveen@linux.ibm.com>
Subject: Re: [PATCH v3 1/4] powerpc/pseries: Limit PVR list to 16 entries for CAS negotiation
Date: Wed, 5 Aug 2026 19:39:21 +0530	[thread overview]
Message-ID: <20260805193834.b80d421d-21-amachhiw@linux.ibm.com> (raw)
In-Reply-To: <20260805110924.3853410-2-mahesh@linux.ibm.com>

On 2026/08/05 04:39 PM, Mahesh Salgaonkar wrote:
> Current Power system firmware caps the PVR list array size at 16 entries
> during CAS (Client Architecture Support) negotiation. Passing more than
> capped size to older firmware could cause an undefined behaviour and
> breaks compatibility.
> 
> Future Power system firmware releases will lift this restriction and
> support greater than 16 array entries.
> 
> Ensure that when running on Power11 or below hardware, the number
> of PVR entries passed during CAS negotiation does not exceed the
> firmware-imposed limit of 16.
> 
> In prom_send_capabilities(), compute start_index to skip the oldest
> leading pvrs[] entries when running on Power11 or below hardware, so
> that the pointer passed to ibm,client-architecture-support points to
> ibm_architecture_vec.pvrs[start_index], presenting exactly 16 entries to
> firmware.
> 
> Signed-off-by: Mahesh Salgaonkar <mahesh@linux.ibm.com>
> Tested-by: Praveen K Pandey <praveen@linux.ibm.com>
> ---
> Change in v3:
> - Remove unintentional whitespace change.
> 
> Change in v2:
> - Define a named macro CAS_MAX_PVR_ENTRIES
> ---
>  arch/powerpc/kernel/prom_init.c | 34 +++++++++++++++++++++++++++------
>  1 file changed, 28 insertions(+), 6 deletions(-)

Reviewed-by: Amit Machhiwal <amachhiw@linux.ibm.com>

~Amit


  parent reply	other threads:[~2026-08-05 14:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-05 11:09 [PATCH v3 0/4] Base support for Power12 Mahesh Salgaonkar
2026-08-05 11:09 ` [PATCH v3 1/4] powerpc/pseries: Limit PVR list to 16 entries for CAS negotiation Mahesh Salgaonkar
2026-08-05 12:03   ` Nikhil Kumar Singh
2026-08-05 14:09   ` Amit Machhiwal [this message]
2026-08-05 11:09 ` [PATCH v3 2/4] powerpc: Add Power12 raw mode Mahesh Salgaonkar
2026-08-05 11:09 ` [PATCH v3 3/4] powerpc: Add Power12 architected mode Mahesh Salgaonkar
2026-08-05 11:09 ` [PATCH v3 4/4] powerpc/perf: Add power12 Base Performance Monitoring support Mahesh Salgaonkar
2026-08-05 12:04   ` Nikhil Kumar Singh

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=20260805193834.b80d421d-21-amachhiw@linux.ibm.com \
    --to=amachhiw@linux.ibm.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=maddy@linux.ibm.com \
    --cc=mahesh@linux.ibm.com \
    --cc=praveen@linux.ibm.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