qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
	deller@kernel.org, qemu-devel@nongnu.org
Cc: Richard Henderson <richard.henderson@linaro.org>
Subject: Re: [PATCH 1/2] hw/hppa: Support up to 256 GiB RAM on 64-bit machines
Date: Fri, 24 Jan 2025 19:18:43 +0100	[thread overview]
Message-ID: <33756833-6110-499c-a90e-042f2d12b7c1@gmx.de> (raw)
In-Reply-To: <32a9172f-367d-4344-ae63-a9d98dfe8d9a@linaro.org>

On 1/24/25 18:52, Philippe Mathieu-Daudé wrote:
> On 22/1/25 19:09, deller@kernel.org wrote:
>> From: Helge Deller <deller@gmx.de>
>>
>> Allow up to 256 GB RAM, which is the maximum a rp8440 machine (the very
>> last 64-bit PA-RISC machine) physically supports.
>>
>> Signed-off-by: Helge Deller <deller@gmx.de>
>> ---
>>   hw/hppa/hppa_hardware.h |  2 ++
>>   hw/hppa/machine.c       | 26 +++++++++++++++++++-------
>>   2 files changed, 21 insertions(+), 7 deletions(-)
>>
>> diff --git a/hw/hppa/hppa_hardware.h b/hw/hppa/hppa_hardware.h
>> index a9be7bb851..a276240967 100644
>> --- a/hw/hppa/hppa_hardware.h
>> +++ b/hw/hppa/hppa_hardware.h
>> @@ -49,4 +49,6 @@
>>   #define CPU_HPA_CR_REG  7       /* store CPU HPA in cr7 (SeaBIOS internal) */
>>   #define PIM_STORAGE_SIZE 600    /* storage size of pdc_pim_toc_struct (64bit) */
>> +#define RAM_MAP_HIGH  0x0100000000  /* memory above 3.75 GB is mapped here */
>
> Should we use ull suffix?

I prefer not to add this suffix, as this file is shared as-is with SeaBIOS-hppa
sources and included by the hppa assembler.

Helge


  reply	other threads:[~2025-01-24 18:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 18:09 [PATCH 0/2] hppa updates deller
2025-01-22 18:09 ` [PATCH 1/2] hw/hppa: Support up to 256 GiB RAM on 64-bit machines deller
2025-01-24 17:49   ` Richard Henderson
2025-01-24 17:52   ` Philippe Mathieu-Daudé
2025-01-24 18:18     ` Helge Deller [this message]
2025-01-22 18:09 ` [PATCH 2/2] hw/hppa: Fix booting Linux kernel with initrd deller
2025-01-24 17:49   ` Richard Henderson
2025-10-08 13:43   ` Philippe Mathieu-Daudé
2025-10-08 13:49     ` Helge Deller
2025-10-08 14:33       ` Philippe Mathieu-Daudé

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=33756833-6110-499c-a90e-042f2d12b7c1@gmx.de \
    --to=deller@gmx.de \
    --cc=deller@kernel.org \
    --cc=philmd@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.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).