On Thu, 29 May 2025 11:29:58 +0100,
Ganapatrao Kulkarni <gankulkarni@xxxxxxxxxxxxxxxxxxxxxx> wrote:
Hi Eric,
On 5/28/2025 6:58 PM, Eric Auger wrote:
Hi Ganapatrao,
On 5/12/25 12:52 PM, Ganapatrao Kulkarni wrote:
This patch series makes the selftest work with NV enabled. The guest code
is run in vEL2 instead of EL1. We add a command line option to enable
testing of NV. The NV tests are disabled by default.
For commodity, I would add in the coverletter that for all tests
enhanced with vEL2 testing "-g 1" option shall be added to force that mode.
Sure, will do.
There is no selection as such. I have worked on around 50% of the tests and sent for the early review.
I don't really get how you chose tests capable to run at vEL2 and
excluded others? Wouldn't it make sense to have a way to run all tests
in either mode?
Yes, almost all tests can/should run in vEL2 except few.
Define EL2. You are so far assuming a E2H RES1 guest, and I don't see
anything that is even trying E2H RES0. After all the complaining that
E2H0 wasn't initially supported, this is a bit... disappointing.IIRC, I was mentioning about L1 switching between arch mmu table and guest mmu table(VMID 0).
Also, running EL2 is the least of our worries, because that's pretty
easy to deal with. It is running at EL1/0 when EL2 is present that is
interesting, and I see no coverage on that front.