[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <86h661wje4.wl-maz@kernel.org>
Date: Tue, 14 Jan 2025 14:38:11 +0000
From: Marc Zyngier <maz@...nel.org>
To: Eric Auger <eauger@...hat.com>
Cc: Ganapatrao Kulkarni <gankulkarni@...amperecomputing.com>,
kvmarm <kvmarm@...ts.linux.dev>,
linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org,
oliver.upton@...ux.dev,
christoffer.dall@....com,
suzuki.poulose@....com,
will@...nel.org,
catalin.marinas@....com,
coltonlewis@...gle.com,
joey.gouly@....com,
yuzenghui@...wei.com,
darren@...amperecomputing.com,
vishnu@...amperecomputing.com
Subject: Re: [PATCH] KVM: arm64: nv: Set ISTATUS for emulated timers, If timer expired
Hi Eric,
On Tue, 14 Jan 2025 13:12:21 +0000,
Eric Auger <eauger@...hat.com> wrote:
>
> I also confirm that using a mailine edk2 fixed the issues I faced
> previously (fed/rhel L1 guest not booting).
>
> I used Marc's nv-next branch and qemu rebase.
When did you sample this branch? It is almost daily rebased at the
moment, given that we keep piling up things in kvmarm/next.
> With a rhel L1 guest I can now boot buildroot, debian and rhel guest as
> L2 (feat mainline edk2). For rhel, I tested different kinds of page size
> combinations for L1/L2 (4k and 64kB) and it worked.
>
> I tested on AmpereOne and Grace-Hopper systems
Thanks for the confirmation. I haven't had a chance to try QEMU yet,
but I expect that save/restore will not work. Something to look into,
I guess.
M.
--
Without deviation from the norm, progress is not possible.
Powered by blists - more mailing lists