From: Raghavendra Rao Ananta <rananta@google.com>
To: Oliver Upton <oliver.upton@linux.dev>, Marc Zyngier <maz@kernel.org>
Cc: Raghavendra Rao Anata <rananta@google.com>,
Mingwei Zhang <mizhang@google.com>,
linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Subject: [PATCH 0/2] KVM : selftests: arm64: Explicitly set the page attrs to Inner-Shareable
Date: Fri, 4 Apr 2025 22:06:57 +0000 [thread overview]
Message-ID: <20250404220659.1312465-1-rananta@google.com> (raw)
The series fixes a conflict in memory attributes in some implementations,
such as Neoverse-N3, that causes a data abort in guest EL1 with FSC
0x35 (IMPLEMENTATION DEFINED fault (Unsupported Exclusive or Atomic
access)).
Patch-1 is a cleanup patch that replaces numbers (and comments) to
using proper macros for hardware configuration, such as registers and
page-table entries.
Patch-2 fixes the actual bug and sets the page attrs to Inner-Shareable
by default for the VMs created in the selftests. More details are
presented in the commit text.
Raghavendra Rao Ananta (2):
KVM: selftests: arm64: Introduce and use hardware-definition macros
KVM: selftests: arm64: Explicitly set the page attrs to
Inner-Shareable
tools/arch/arm64/include/asm/sysreg.h | 38 ++++++++++++
.../selftests/kvm/arm64/page_fault_test.c | 2 +-
.../selftests/kvm/include/arm64/processor.h | 29 +++++++--
.../selftests/kvm/lib/arm64/processor.c | 60 +++++++++++--------
4 files changed, 96 insertions(+), 33 deletions(-)
base-commit: 38fec10eb60d687e30c8c6b5420d86e8149f7557
--
2.49.0.504.g3bcea36a83-goog
next reply other threads:[~2025-04-04 22:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 22:06 Raghavendra Rao Ananta [this message]
2025-04-04 22:06 ` [PATCH 1/2] KVM: selftests: arm64: Introduce and use hardware-definition macros Raghavendra Rao Ananta
2025-04-04 22:46 ` Oliver Upton
2025-04-04 22:06 ` [PATCH 2/2] KVM: selftests: arm64: Explicitly set the page attrs to Inner-Shareable Raghavendra Rao Ananta
2025-04-04 23:01 ` Oliver Upton
2025-04-05 0:01 ` Raghavendra Rao Ananta
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=20250404220659.1312465-1-rananta@google.com \
--to=rananta@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=mizhang@google.com \
--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 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).