From: James Clark <james.clark@linaro.org>
To: Oliver Upton <oliver.upton@linux.dev>
Cc: kvmarm@lists.linux.dev,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
will@kernel.org, tabba@google.com, maz@kernel.org
Subject: Re: [bug report] KVM: arm64: BUG when reading kcore with kvm-arm.mode=protected
Date: Fri, 4 Oct 2024 16:41:10 +0100 [thread overview]
Message-ID: <cd1dda81-e23d-4f97-96b2-bf6e2002ea99@linaro.org> (raw)
In-Reply-To: <Zv1qeOOHjF0mv5Su@linux.dev>
On 02/10/2024 16:44, Oliver Upton wrote:
> +cc relevant folks
>
> Hi James,
>
> On Wed, Oct 02, 2024 at 02:23:32PM +0100, James Clark wrote:
>> Hi,
>>
>> I noticed this when running the Perf tests so I'm reporting it here (I don't
>> actually need kcore FWIW). I tested from 6.1 to 6.11 with the same results:
>
> Yeah, this is (somewhat) intended behavior. By reading kcore you wind up
> reading from memory that isn't in a visible state for the host (e.g. hyp
> text).
>
> Protected mode is very much a WIP, and is expected to be rough around the
> edges like this. Eventually the hypervisor will inject an abort into the
> host for disallowed memory accesses instead of tripping a BUG_ON(). We
> don't have that upstream right now.
>
Thanks for the confirmation. I assumed as much but just wanted to be sure.
prev parent reply other threads:[~2024-10-04 17:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-02 13:23 [bug report] KVM: arm64: BUG when reading kcore with kvm-arm.mode=protected James Clark
2024-10-02 15:44 ` Oliver Upton
2024-10-04 15:41 ` James Clark [this message]
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=cd1dda81-e23d-4f97-96b2-bf6e2002ea99@linaro.org \
--to=james.clark@linaro.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=tabba@google.com \
--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 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).