qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Shivaprasad G Bhat <sbhat@linux.ibm.com>
To: Harsh Prateek Bora <harshpb@linux.ibm.com>,
	qemu-ppc@nongnu.org, npiggin@gmail.com
Cc: danielhb413@gmail.com, qemu-devel@nongnu.org
Subject: Re: [PATCH] ppc/spapr: init lrdr-capapcity phys with ram size if maxmem not provided
Date: Thu, 11 Sep 2025 15:49:19 +0530	[thread overview]
Message-ID: <57e06839-34f3-4da9-9304-8ba15d957879@linux.ibm.com> (raw)
In-Reply-To: <20250506042903.76250-1-harshpb@linux.ibm.com>

On 5/6/25 9:59 AM, Harsh Prateek Bora wrote:
> lrdr-capacity contains phys field which communicates the maximum address
> in bytes and therefore, the most memory that can be allocated to this
> partition. This is usually populated when maxmem is provided alongwith
> memory size on qemu command line. However since maxmem is an optional
> param, this leads to bits being set to 0 in absence of maxmem param.
> Fix this by initializing the respective bits as per total mem size in
> such case.
>
> Reported-by: Gaurav Batra <gbatra@us.ibm.com>
> Tested-by: David Christensen <drc@linux.ibm.com>
> Signed-off-by: Harsh Prateek Bora <harshpb@linux.ibm.com>
> ---
>   hw/ppc/spapr.c | 11 +++++++----
>   1 file changed, 7 insertions(+), 4 deletions(-)
>
> diff --git a/hw/ppc/spapr.c b/hw/ppc/spapr.c
> index 702f774cda..9f18642734 100644
> --- a/hw/ppc/spapr.c
> +++ b/hw/ppc/spapr.c
> @@ -907,6 +907,7 @@ static void spapr_dt_rtas(SpaprMachineState *spapr, void *fdt)
>       int rtas;
>       GString *hypertas = g_string_sized_new(256);
>       GString *qemu_hypertas = g_string_sized_new(256);
> +    uint64_t max_device_addr = 0;
>       uint32_t lrdr_capacity[] = {
>           0,
>           0,
> @@ -917,13 +918,15 @@ static void spapr_dt_rtas(SpaprMachineState *spapr, void *fdt)
>   
>       /* Do we have device memory? */
>       if (MACHINE(spapr)->device_memory) {
> -        uint64_t max_device_addr = MACHINE(spapr)->device_memory->base +
> +        max_device_addr = MACHINE(spapr)->device_memory->base +
>               memory_region_size(&MACHINE(spapr)->device_memory->mr);
> -
> -        lrdr_capacity[0] = cpu_to_be32(max_device_addr >> 32);
> -        lrdr_capacity[1] = cpu_to_be32(max_device_addr & 0xffffffff);
> +    } else if (ms->ram_size == ms->maxram_size) {
> +        max_device_addr = ms->ram_size;
>       }
>   
> +    lrdr_capacity[0] = cpu_to_be32(max_device_addr >> 32);
> +    lrdr_capacity[1] = cpu_to_be32(max_device_addr & 0xffffffff);
> +

Since maxmem accounts for pcdimm and/or nvdimm cases, this would work

fine for all probable scenarios in this code path.


Reviewed-by: Shivaprasad G Bhat <sbhat@linux.ibm.com>


Thanks,

Shivaprasad



      reply	other threads:[~2025-09-11 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06  4:29 [PATCH] ppc/spapr: init lrdr-capapcity phys with ram size if maxmem not provided Harsh Prateek Bora
2025-09-11 10:19 ` Shivaprasad G Bhat [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=57e06839-34f3-4da9-9304-8ba15d957879@linux.ibm.com \
    --to=sbhat@linux.ibm.com \
    --cc=danielhb413@gmail.com \
    --cc=harshpb@linux.ibm.com \
    --cc=npiggin@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.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;
as well as URLs for NNTP newsgroup(s).