From: Dan Carpenter <dan.carpenter@linaro.org>
To: Marc Zyngier <maz@kernel.org>
Cc: Naresh Kamboju <naresh.kamboju@linaro.org>,
kvmarm@lists.linux.dev,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>,
virtualization@lists.linux.dev, Mark Brown <broonie@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Arnd Bergmann <arnd@arndb.de>,
Anders Roxell <anders.roxell@linaro.org>,
Aishwarya TCV <Aishwarya.TCV@arm.com>
Subject: Re: kvm: nVHE hyp panic at: __kvm_nvhe_kvm_hyp_handle_sysre
Date: Wed, 12 Feb 2025 14:31:30 +0300 [thread overview]
Message-ID: <6b7780ee-6dbe-4e2a-8d7f-4057e83c767e@stanley.mountain> (raw)
In-Reply-To: <8634gku30g.wl-maz@kernel.org>
On Tue, Feb 11, 2025 at 11:36:31AM +0000, Marc Zyngier wrote:
> On Tue, 11 Feb 2025 11:24:06 +0000,
> Naresh Kamboju <naresh.kamboju@linaro.org> wrote:
> >
> > Regression on rk3399-rock-pi-4b while running kvm-unit-tests with
> > nvhe, protected and vhe mode with virtualization enabled.
>
> I do not buy this. RK3399 only has ARMv8.0 cores, which by definition
> do not have VHE.
>
The links to the dmesg are at the bottom of the email. It does seem to
be a RK3399 with ARMv8.0 cores though as you say...
https://lkft.validation.linaro.org/scheduler/job/8117232#L1395
We'll test the patch.
regards,
dan carpenter
next prev parent reply other threads:[~2025-02-12 11:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-11 11:24 Naresh Kamboju
2025-02-11 11:36 ` Marc Zyngier
2025-02-12 11:31 ` Dan Carpenter [this message]
2025-02-12 11:41 ` Dan Carpenter
2025-02-12 11:42 ` Naresh Kamboju
2025-02-12 14:00 ` Marc Zyngier
2025-02-13 8:52 ` Naresh Kamboju
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=6b7780ee-6dbe-4e2a-8d7f-4057e83c767e@stanley.mountain \
--to=dan.carpenter@linaro.org \
--cc=Aishwarya.TCV@arm.com \
--cc=anders.roxell@linaro.org \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=naresh.kamboju@linaro.org \
--cc=virtualization@lists.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
all inboxes | Powered by JetHome®