From: Marc Zyngier <maz@kernel.org>
To: Jan Kotas <jank@cadence.com>
Cc: Oliver Upton <oliver.upton@linux.dev>,
"kvmarm@lists.linux.dev" <kvmarm@lists.linux.dev>
Subject: Re: HCR_EL2 GET_ONE_REG value difference
Date: Fri, 10 Oct 2025 10:37:31 +0100 [thread overview]
Message-ID: <86ikgnxfl0.wl-maz@kernel.org> (raw)
In-Reply-To: <47FBDCE7-F8D8-4071-93D8-E4E494D41F34@global.cadence.com>
On Fri, 10 Oct 2025 09:30:12 +0100,
Jan Kotas <jank@cadence.com> wrote:
>
> Hello,
>
> During NV debugging I noticed a difference in HCR_EL2 value.
>
> The value I get from accessing this register, using KVM_GET_ONE_REG:
> 0x30480000000
These bits are API, APK, E2H, RW.
When did you access this? After the vcpu has run? Before it has run?
What NV configuration did you use?
>
> However, X1 value after executing mrs x1, hcr_el2 in guest:
> 0x100030080000000
You have ATA, API, APK, RW. Is that the *only* thing that has run in
your guest?
> I access both of these at the same place.
"at the same place"? What do you mean? One is accessed from host
userspace, and the other from the guest. How can that be the same
place?
> I get the list of available registers from KVM_GET_REG_LIST.
>
> I double checked my encoding, and it seems to be correct.
> HCR_EL2 3, 4, 1, 1, 0
>
> I can check other registers, but I first wanted to check, if this expected?
> Is there something I’m missing, when accessing emulated registers?
Could you please start by clarifying what you are doing?
Thanks,
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-10-10 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-10 8:30 HCR_EL2 GET_ONE_REG value difference Jan Kotas
2025-10-10 9:37 ` Marc Zyngier [this message]
2025-10-10 9:51 ` Jan Kotas
2025-10-10 10:31 ` Marc Zyngier
2025-10-10 10:59 ` Jan Kotas
2025-10-10 11:59 ` Marc Zyngier
2025-10-10 12:49 ` Jan Kotas
2025-10-10 13:12 ` 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=86ikgnxfl0.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=jank@cadence.com \
--cc=kvmarm@lists.linux.dev \
--cc=oliver.upton@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 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.