From: Marc Zyngier <maz@kernel.org>
To: Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>
Cc: kvmarm <kvmarm@lists.linux.dev>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, oliver.upton@linux.dev,
christoffer.dall@arm.com, suzuki.poulose@arm.com,
will@kernel.org, catalin.marinas@arm.com, coltonlewis@google.com,
joey.gouly@arm.com, yuzenghui@huawei.com,
darren@os.amperecomputing.com, vishnu@os.amperecomputing.com
Subject: Re: [PATCH] KVM: arm64: nv: Set ISTATUS for emulated timers, If timer expired
Date: Mon, 09 Dec 2024 15:52:19 +0000 [thread overview]
Message-ID: <86zfl4svkc.wl-maz@kernel.org> (raw)
In-Reply-To: <8be59ff3-6a68-48e1-8181-0ce4b2e7180f@os.amperecomputing.com>
On Mon, 09 Dec 2024 15:39:28 +0000,
Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com> wrote:
>
>
>
> On 09-12-2024 06:50 pm, Marc Zyngier wrote:
> > On Mon, 09 Dec 2024 12:25:34 +0000,
> > Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com> wrote:
> >>>>
> >>>> During automated testing of Nested Virtualization using avocado-vt,
> >>>
> >>> Which is not merged upstream. So what branch are you using? Based on
> >>> what kernel version? On what HW? With which virtualisation features?
> >>>
> >>
> >> Testing is done on Ampere's AmpereOne platform using 6.10 based kernel
> >> with NV patches from your repo.
> >
> > Grmbl... *Which* patches? At least give me the SHA1 of the branch,
> > because I have no idea what you are running. And 6.10 is definitely
> > not something I care about. If you're using the NV patches, the
> > *minimum* you should run is 6.13-rc1, because that's what the current
> > code is based on.
> >
>
> I tried 6.13-rc1 based nv-next branch today, which failed to boot
> UEFI as L1. Yet to debug this.
Works nicely here with kvmtool as the VMM. From what I understand,
EDK2 needs some surgery to correctly boot at EL2 without FEAT_E2H0.
> We do have the FEAT_ECV on AmpereOne, I was the one reported/fixed bug
> with FEAT_ECV(CNTPOFF offset issue) in the past.
Sorry, I don't keep track of the feature set for machines I don't have
access to.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2024-12-09 15:53 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 5:32 [PATCH] KVM: arm64: nv: Set ISTATUS for emulated timers, If timer expired Ganapatrao Kulkarni
2024-12-09 9:54 ` Marc Zyngier
2024-12-09 12:25 ` Ganapatrao Kulkarni
2024-12-09 13:20 ` Marc Zyngier
2024-12-09 15:23 ` Marc Zyngier
2024-12-09 15:39 ` Ganapatrao Kulkarni
2024-12-09 15:52 ` Marc Zyngier [this message]
2024-12-09 16:46 ` Eric Auger
2024-12-09 17:30 ` Marc Zyngier
2024-12-09 17:34 ` Eric Auger
2024-12-19 9:30 ` Ganapatrao Kulkarni
2024-12-19 12:23 ` Marc Zyngier
2025-01-14 13:12 ` Eric Auger
2025-01-14 14:38 ` Marc Zyngier
2025-01-14 14:57 ` Eric Auger
2025-01-14 15:52 ` Marc Zyngier
2025-01-16 17:52 ` Eric Auger
2025-01-16 18:25 ` Marc Zyngier
2025-02-07 17:45 ` Marc Zyngier
2025-02-07 18:09 ` Oliver Upton
2025-02-07 18:38 ` Marc Zyngier
2025-02-07 19:08 ` Oliver Upton
2025-02-10 18:26 ` Eric Auger
2025-02-11 19:20 ` Marc Zyngier
2025-02-15 17:50 ` Marc Zyngier
2025-02-18 7:33 ` Ganapatrao Kulkarni
2025-02-18 16:33 ` Marc Zyngier
2025-02-18 21:24 ` Marc Zyngier
2025-02-20 6:10 ` Ganapatrao Kulkarni
2025-02-10 13:18 ` Eric Auger
2024-12-10 12:48 ` Ganapatrao Kulkarni
2024-12-09 19:36 ` kernel test robot
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=86zfl4svkc.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=christoffer.dall@arm.com \
--cc=coltonlewis@google.com \
--cc=darren@os.amperecomputing.com \
--cc=gankulkarni@os.amperecomputing.com \
--cc=joey.gouly@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver.upton@linux.dev \
--cc=suzuki.poulose@arm.com \
--cc=vishnu@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yuzenghui@huawei.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).