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:41:38 +0300 [thread overview]
Message-ID: <3902208d-8814-46fe-ba98-3db833b9a886@stanley.mountain> (raw)
In-Reply-To: <8634gku30g.wl-maz@kernel.org>
On Tue, Feb 11, 2025 at 11:36:31AM +0000, Marc Zyngier wrote:
> For the crash at hand, which clearly shows nVHE, can you report
> whether the following hack fixes it for you?
>
> M.
No luck, I'm afraid. It still crashes the same way.
https://tuxapi.tuxsuite.com/v1/groups/linaro/projects/anders/tests/2steTT4f2J8ZJjc3jNJFMuow9Cb
Click on "Logs: html" for the dmesg.
regards,
dan carpenter
>
> diff --git a/arch/arm64/kvm/hyp/include/hyp/switch.h b/arch/arm64/kvm/hyp/include/hyp/switch.h
> index f838a45665f26..cb57420a07de2 100644
> --- a/arch/arm64/kvm/hyp/include/hyp/switch.h
> +++ b/arch/arm64/kvm/hyp/include/hyp/switch.h
> @@ -556,7 +556,7 @@ static bool kvm_handle_cntxct(struct kvm_vcpu *vcpu)
> return false;
> }
>
> - val = compute_counter_value(ctxt);
> + val = compute_counter_value(kern_hyp_va(ctxt));
>
> vcpu_set_reg(vcpu, kvm_vcpu_sys_get_rt(vcpu), val);
> __kvm_skip_instr(vcpu);
>
> --
> Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-02-12 11:41 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
2025-02-12 11:41 ` Dan Carpenter [this message]
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=3902208d-8814-46fe-ba98-3db833b9a886@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®