All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled
Date: Wed, 18 Aug 2021 10:10:40 +0100	[thread overview]
Message-ID: <162927783509.2863.13074937375734887703.b4-ty@kernel.org> (raw)
In-Reply-To: <20210813130336.8139-1-will@kernel.org>

On Fri, 13 Aug 2021 14:03:36 +0100, Will Deacon wrote:
> When protected mode is enabled, the host is unable to access most parts
> of the EL2 hypervisor image, including 'hyp_physvirt_offset' and the
> contents of the hypervisor's '.rodata.str' section. Unfortunately,
> nvhe_hyp_panic_handler() tries to read from both of these locations when
> handling a BUG() triggered at EL2; the former for converting the ELR to
> a physical address and the latter for displaying the name of the source
> file where the BUG() occurred.
> 
> [...]

Applied to kvm-arm64/mmu/el2-tracking, thanks!

[1/1] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled
      commit: ccac96977243d7916053550f62e6489760ad0adc

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.


_______________________________________________
kvmarm mailing list
kvmarm@lists.cs.columbia.edu
https://lists.cs.columbia.edu/mailman/listinfo/kvmarm

WARNING: multiple messages have this Message-ID (diff)
From: Marc Zyngier <maz@kernel.org>
To: Will Deacon <will@kernel.org>
Cc: kvmarm@lists.cs.columbia.edu, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled
Date: Wed, 18 Aug 2021 10:10:40 +0100	[thread overview]
Message-ID: <162927783509.2863.13074937375734887703.b4-ty@kernel.org> (raw)
In-Reply-To: <20210813130336.8139-1-will@kernel.org>

On Fri, 13 Aug 2021 14:03:36 +0100, Will Deacon wrote:
> When protected mode is enabled, the host is unable to access most parts
> of the EL2 hypervisor image, including 'hyp_physvirt_offset' and the
> contents of the hypervisor's '.rodata.str' section. Unfortunately,
> nvhe_hyp_panic_handler() tries to read from both of these locations when
> handling a BUG() triggered at EL2; the former for converting the ELR to
> a physical address and the latter for displaying the name of the source
> file where the BUG() occurred.
> 
> [...]

Applied to kvm-arm64/mmu/el2-tracking, thanks!

[1/1] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled
      commit: ccac96977243d7916053550f62e6489760ad0adc

Cheers,

	M.
-- 
Without deviation from the norm, progress is not possible.



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2021-08-18  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 13:03 [PATCH] KVM: arm64: Make hyp_panic() more robust when protected mode is enabled Will Deacon
2021-08-13 13:03 ` Will Deacon
2021-08-18  9:10 ` Marc Zyngier [this message]
2021-08-18  9:10   ` 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=162927783509.2863.13074937375734887703.b4-ty@kernel.org \
    --to=maz@kernel.org \
    --cc=kvmarm@lists.cs.columbia.edu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.