qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Pierrick Bouvier <pierrick.bouvier@linaro.org>
To: Mohamed Mediouni <mohamed@unpredictable.fr>
Cc: qemu-devel@nongnu.org, "Daniel P. Berrangé" <berrange@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	"Sunil Muthuswamy" <sunilmut@microsoft.com>,
	"Marc-André Lureau" <marcandre.lureau@redhat.com>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Peter Maydell" <peter.maydell@linaro.org>,
	qemu-arm@nongnu.org
Subject: Re: [RFC 0/9] WHPX support for Arm
Date: Fri, 1 Aug 2025 13:10:13 -0700	[thread overview]
Message-ID: <25a6dd9c-a435-4f2e-9c7c-b92daf5128c1@linaro.org> (raw)
In-Reply-To: <5133CBA1-A4FA-4789-AA7D-2FDBBFDF2470@unpredictable.fr>

On 8/1/25 12:57 PM, Mohamed Mediouni wrote:
> 
> 
>> On 1. Aug 2025, at 21:42, Pierrick Bouvier <pierrick.bouvier@linaro.org> wrote:
>>
>> On 8/1/25 12:31 PM, Mohamed Mediouni wrote:
>>>>> I didn’t test anything on the stable branch for now but only on Canary so far.
>>>>> Just cursorily tested (EDK2 only) an X Elite device on prod (26100.4652) and this issue doesn’t appear.
>>>>> I have 8cx Gen 3 and 8cx Gen 1 (SQ1) devices around, will test on those older SoCs later and see.
>>>>> Random idea for testing: what if you put -M highmem=off, does that change anything?
>>>>>
>>>>
>>>> Good guess, it solves the problem with edk2, and direct boots linux kernel successfully now.
>>>>
>>> If you don’t mind, could you please test the latest commit I just put on the Git repo (whpx branch)? It should address this properly.
>>
>> Sure.
>> Without highmem=off, I get a new error:
>> Physical address width: 36
>> C:\msys64\home\tcwg\qemu\build\qemu-system-aarch64.exe: VCPU supports less PA bits (36) than requested by the memory map (40)
>>
> Oh this confirms what I thought, just pushed a new commit which should be a complete fix. :)
>

It works fine now, on top of c6e3d4d.
Excellent work!

> And accessorily is also a good thing for Snapdragon X too, as 40 VA bits were used there despite the hardware having 39.
>

Yes.

> Thank you,
> -Mohamed

This seems like a good time for cleaning up, address the few comments 
that have been made, and send a v2.
Feel free to add the gic related patches in it, so we have a "complete" 
series to review.

Thanks,
Pierrick


      reply	other threads:[~2025-08-01 21:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-31  5:27 [RFC 0/9] WHPX support for Arm Mohamed Mediouni
2025-07-31  5:27 ` [RFC 1/9] whpx: Move around files before introducing AArch64 support Mohamed Mediouni
2025-07-31  8:27   ` Philippe Mathieu-Daudé
2025-08-01  5:44   ` Richard Henderson
2025-07-31  5:27 ` [RFC 2/9] whpx: reshuffle common code Mohamed Mediouni
2025-07-31  5:27 ` [RFC 3/9] whpx: common: use whpx_cpu_instance_init on x86 only Mohamed Mediouni
2025-07-31  8:30   ` Philippe Mathieu-Daudé
2025-07-31  5:27 ` [RFC 4/9] whpx: interrupt controller support Mohamed Mediouni
2025-07-31  5:27 ` [RFC 5/9] hw/virt: make Qemu aware that WHPX has a vGICv3 Mohamed Mediouni
2025-07-31  8:35   ` Philippe Mathieu-Daudé
2025-07-31 14:47     ` Mohamed Mediouni
2025-07-31  5:27 ` [RFC 6/9] hw: intc: arm_gicv3_common: add whpx Mohamed Mediouni
2025-07-31  8:33   ` Philippe Mathieu-Daudé
2025-07-31  5:27 ` [RFC 7/9] whpx: add arm64 support Mohamed Mediouni
2025-08-01  6:03   ` Richard Henderson
2025-07-31  5:27 ` [RFC 8/9] whpx: copy over memory tracking logic from hvf Mohamed Mediouni
2025-07-31  5:27 ` [RFC 9/9] target/arm: cpu: mark WHPX as supporting PSCI 1.1 Mohamed Mediouni
2025-08-01  1:15 ` [RFC 0/9] WHPX support for Arm Pierrick Bouvier
2025-08-01 12:43   ` Mohamed Mediouni
2025-08-01 17:22     ` Pierrick Bouvier
2025-08-01 18:52       ` Mohamed Mediouni
2025-08-01 19:16         ` Pierrick Bouvier
2025-08-01 19:31           ` Mohamed Mediouni
2025-08-01 19:42             ` Pierrick Bouvier
2025-08-01 19:57               ` Mohamed Mediouni
2025-08-01 20:10                 ` Pierrick Bouvier [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=25a6dd9c-a435-4f2e-9c7c-b92daf5128c1@linaro.org \
    --to=pierrick.bouvier@linaro.org \
    --cc=berrange@redhat.com \
    --cc=marcandre.lureau@redhat.com \
    --cc=mohamed@unpredictable.fr \
    --cc=pbonzini@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sunilmut@microsoft.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;
as well as URLs for NNTP newsgroup(s).