From: Zenghui Yu <zenghui.yu@linux.dev>
To: phil@philjordan.eu
Cc: qemu-devel@nongnu.org, Cameron Esfahani <dirty@apple.com>,
Roman Bolshakov <rbolshakov@ddn.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Marcel Apfelbaum <marcel.apfelbaum@gmail.com>,
Alexander Graf <agraf@csgraf.de>,
Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org
Subject: Re: [PATCH 02/11] arm/hvf: Initialise GICv3 state just before first vCPU run
Date: Wed, 5 Feb 2025 22:47:48 +0800 [thread overview]
Message-ID: <1080d4d7-81d0-4497-bef9-22191a4b999e@linux.dev> (raw)
In-Reply-To: <20241209203629.74436-3-phil@philjordan.eu>
On 2024/12/10 04:36, phil@philjordan.eu wrote:
> From: Phil Dennis-Jordan <phil@philjordan.eu>
>
> Initialising the vCPU PFR0_EL1 system register with the GIC flag in
> hvf_arch_init_vcpu() does not actually work because the GIC state is
> not yet available at that time.
>
> If we set this flag just before running each vCPU for the first time,
> the GIC will definitely be fully initialised at that point.
>
> Signed-off-by: Phil Dennis-Jordan <phil@philjordan.eu>
> ---
> target/arm/hvf/hvf.c | 17 ++++++++++-------
> 1 file changed, 10 insertions(+), 7 deletions(-)
Tested-by: Zenghui Yu <zenghui.yu@linux.dev>
Thanks!
next prev parent reply other threads:[~2025-02-05 14:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 20:36 [PATCH 00/11] hvf and APIC fixes, improvements, and optimisations phil
2024-12-09 20:36 ` [PATCH 01/11] hvf: Add facility for initialisation code prior to first vCPU run phil
2024-12-10 10:05 ` Alexander Graf
2025-02-05 21:02 ` Philippe Mathieu-Daudé
2025-02-09 19:45 ` Phil Dennis-Jordan
2024-12-09 20:36 ` [PATCH 02/11] arm/hvf: Initialise GICv3 state just before " phil
2024-12-10 10:05 ` Alexander Graf
2025-02-05 14:47 ` Zenghui Yu [this message]
2024-12-09 20:36 ` [PATCH 03/11] i386/hvf: Don't send signal to thread when kicking phil
2024-12-09 21:22 ` Philippe Mathieu-Daudé
2024-12-10 8:17 ` Phil Dennis-Jordan
2024-12-10 9:21 ` Roman Bolshakov
2024-12-10 9:52 ` Phil Dennis-Jordan
2025-02-05 20:58 ` Philippe Mathieu-Daudé
2024-12-09 20:36 ` [PATCH 04/11] i386/hvf: Pre-fetch emulated instructions phil
2024-12-09 20:36 ` [PATCH 05/11] i386/hvf: Decode APIC access x86 instruction outside BQL phil
2024-12-09 20:36 ` [PATCH 06/11] i386/hvf: APIC access exit with fast-path for common mov cases phil
2024-12-09 20:36 ` [PATCH 07/11] i386/hvf: Enables APIC_ACCESS VM exits by setting APICBASE phil
2024-12-09 20:36 ` [PATCH 08/11] i386/hvf: Variable type fixup in decoder phil
2024-12-09 20:49 ` Philippe Mathieu-Daudé
2024-12-09 20:36 ` [PATCH 09/11] i386/hvf: Print hex pairs for each opcode byte in decode error phil
2024-12-09 20:54 ` Philippe Mathieu-Daudé
2024-12-10 11:28 ` Phil Dennis-Jordan
2024-12-09 20:36 ` [PATCH 10/11] hw/intc/apic: Fixes magic number use, removes outdated comment phil
2024-12-09 20:55 ` Philippe Mathieu-Daudé
2024-12-09 20:36 ` [PATCH 11/11] hw/intc/apic: Raise exception when setting reserved APICBASE bits phil
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=1080d4d7-81d0-4497-bef9-22191a4b999e@linux.dev \
--to=zenghui.yu@linux.dev \
--cc=agraf@csgraf.de \
--cc=dirty@apple.com \
--cc=marcel.apfelbaum@gmail.com \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=phil@philjordan.eu \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=rbolshakov@ddn.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).