From: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
To: Marc Zyngier <maz@kernel.org>
Cc: kvmarm@lists.linux.dev, kvm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, oliver.upton@linux.dev,
darren@os.amperecomputing.com,
d.scott.phillips@amperecomputing.com
Subject: Re: [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables.
Date: Tue, 26 Mar 2024 17:03:27 +0530 [thread overview]
Message-ID: <92117ba1-54ff-4752-b446-0ed09bde7201@os.amperecomputing.com> (raw)
In-Reply-To: <86r0go201z.wl-maz@kernel.org>
Hi Marc,
On 05-03-2024 08:33 pm, Marc Zyngier wrote:
> On Tue, 05 Mar 2024 13:29:08 +0000,
> Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com> wrote:
>>
>>
>>
>> What are the core issues (please forgive me if you mentioned already)?
>> certainly we will prioritise them than this.
>
> AT is a big one. Maintenance interrupts are more or less broken. I'm
> slowly plugging PAuth, but there's no testing whatsoever (running
> Linux doesn't count). Lack of SVE support is also definitely a
> blocker.
>
I am debugging an issue where EDK2(ArmVirtPkg) boot hangs when tried to
boot from L1 using QEMU.
The hang is due to failure of AT instruction and resulting in immediate
return to Guest(L2) and the loop continues...
AT instruction is executed in function of
__get_fault_info(__translate_far_to_hpfar) in L1 when data abort is
forwarded. Then AT instruction is trapped and executed/emulated in L0 in
function "__kvm_at_s1e01" is failing and resulting in the return to guest.
Is this also the manifestation of the issue of AT that you are referring to?
Thanks,
Ganapat
next prev parent reply other threads:[~2024-03-26 11:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20240305054606.13261-1-gankulkarni@os.amperecomputing.com>
2024-03-05 8:46 ` [RFC PATCH] kvm: nv: Optimize the unmapping of shadow S2-MMU tables Oliver Upton
2024-03-06 5:31 ` Ganapatrao Kulkarni
2024-03-06 8:39 ` Oliver Upton
2024-03-06 13:33 ` Marc Zyngier
2024-03-06 14:57 ` Ganapatrao Kulkarni
2024-03-05 11:13 ` Marc Zyngier
2024-03-05 13:29 ` Ganapatrao Kulkarni
2024-03-05 15:03 ` Marc Zyngier
2024-03-05 18:33 ` Ganapatrao Kulkarni
2024-03-06 10:23 ` Marc Zyngier
2024-03-26 11:33 ` Ganapatrao Kulkarni [this message]
2024-03-27 12:12 ` Marc Zyngier
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=92117ba1-54ff-4752-b446-0ed09bde7201@os.amperecomputing.com \
--to=gankulkarni@os.amperecomputing.com \
--cc=d.scott.phillips@amperecomputing.com \
--cc=darren@os.amperecomputing.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
/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