From: Zenghui Yu <yuzenghui@huawei.com>
To: Jiaqi Yan <jiaqiyan@google.com>
Cc: <maz@kernel.org>, <oliver.upton@linux.dev>, <duenwen@google.com>,
<rananta@google.com>, <jthoughton@google.com>,
<vsethi@nvidia.com>, <jgg@nvidia.com>, <joey.gouly@arm.com>,
<suzuki.poulose@arm.com>, <catalin.marinas@arm.com>,
<will@kernel.org>, <pbonzini@redhat.com>, <corbet@lwn.net>,
<shuah@kernel.org>, <kvm@vger.kernel.org>,
<kvmarm@lists.linux.dev>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kselftest@vger.kernel.org>
Subject: Re: [PATCH v4 2/3] KVM: selftests: Test for KVM_EXIT_ARM_SEA
Date: Fri, 12 Dec 2025 17:21:55 +0800 [thread overview]
Message-ID: <dbcfb853-5853-5967-1bf9-76c6b3839717@huawei.com> (raw)
In-Reply-To: <CACw3F51mRXCDz7Hd4Vve98NoskhB2cSc88zAGfd6Hwr4uCBxPA@mail.gmail.com>
On 2025/12/12 9:53, Jiaqi Yan wrote:
> On Thu, Dec 11, 2025 at 5:02 AM Zenghui Yu <yuzenghui@huawei.com> wrote:
> >
> > I can also hit this ASSERT with:
> >
> > Random seed: 0x6b8b4567
> > # Mapped 0x40000 pages: gva=0x80000000 to gpa=0xff80000000
> > # Before EINJect: data=0xbaadcafe
> > # EINJ_GVA=0x81234bad, einj_gpa=0xff81234bad, einj_hva=0xffff41234bad,
> > einj_hpa=0x2841234bad
> > # echo 0x10 > /sys/kernel/debug/apei/einj/error_type - done
> > # echo 0x2 > /sys/kernel/debug/apei/einj/flags - done
> > # echo 0x2841234bad > /sys/kernel/debug/apei/einj/param1 - done
> > # echo 0xffffffffffffffff > /sys/kernel/debug/apei/einj/param2 - done
> > # echo 0x1 > /sys/kernel/debug/apei/einj/notrigger - done
> > # echo 0x1 > /sys/kernel/debug/apei/einj/error_inject - done
> > # Memory UER EINJected
> > # Dump kvm_run info about KVM_EXIT_MMIO
> > # kvm_run.arm_sea: esr=0xffff90ba0040, flags=0x691000
> > # kvm_run.arm_sea: gva=0x100000008, gpa=0
> > ==== Test Assertion Failure ====
> > arm64/sea_to_user.c:207: exit_reason == (41)
> > pid=38023 tid=38023 errno=4 - Interrupted system call
> > 1 0x0000000000402d1b: run_vm at sea_to_user.c:207
> > 2 0x0000000000402467: main at sea_to_user.c:330
> > 3 0x0000ffff9122b03f: ?? ??:0
> > 4 0x0000ffff9122b117: ?? ??:0
> > 5 0x00000000004026ef: _start at ??:?
> > Wanted KVM exit reason: 41 (ARM_SEA), got: 6 (MMIO)
> >
> > Not sure what's wrong it..
>
> Does your test machine have SDEI or SCI enabled for host APEI? Do you
> see any kernel log from "Memory failure:" saying hugetlb page
> recovered, and recovered significant earlier than the KVM exit here.
> It maybe the kernel has already unmapped hugepage in response to SDEI
> or SCI before this test actually consumes memory error, so no SEA is
> actually triggered.
No kernel log was printed when I saw this failure.
Thanks,
Zenghui
next prev parent reply other threads:[~2025-12-12 9:22 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-13 18:59 [PATCH v4 0/3] VMM can handle guest SEA via KVM_EXIT_ARM_SEA Jiaqi Yan
2025-10-13 18:59 ` [PATCH v4 1/3] KVM: arm64: VM exit to userspace to handle SEA Jiaqi Yan
2025-11-03 18:17 ` Jose Marinho
2025-11-03 20:45 ` Jiaqi Yan
2025-11-11 9:53 ` Oliver Upton
2025-11-11 23:32 ` Jiaqi Yan
2025-11-03 22:22 ` Marc Zyngier
2025-10-13 18:59 ` [PATCH v4 2/3] KVM: selftests: Test for KVM_EXIT_ARM_SEA Jiaqi Yan
2025-12-11 13:02 ` Zenghui Yu
2025-12-12 1:53 ` Jiaqi Yan
2025-12-12 9:21 ` Zenghui Yu [this message]
2025-12-12 22:42 ` Jiaqi Yan
2025-10-13 18:59 ` [PATCH v4 3/3] Documentation: kvm: new UAPI for handling SEA Jiaqi Yan
2025-10-14 1:51 ` Randy Dunlap
2025-10-21 16:13 ` Jiaqi Yan
2025-10-20 14:46 ` [PATCH v4 0/3] VMM can handle guest SEA via KVM_EXIT_ARM_SEA Jason Gunthorpe
2025-11-10 17:41 ` Jiaqi Yan
2025-11-13 13:54 ` Mauro Carvalho Chehab
2025-11-13 18:21 ` Oliver Upton
2025-11-13 21:06 ` Oliver Upton
2025-11-13 22:14 ` Jiaqi Yan
2025-11-13 22:33 ` Oliver Upton
2025-11-14 0:53 ` Jiaqi Yan
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=dbcfb853-5853-5967-1bf9-76c6b3839717@huawei.com \
--to=yuzenghui@huawei.com \
--cc=catalin.marinas@arm.com \
--cc=corbet@lwn.net \
--cc=duenwen@google.com \
--cc=jgg@nvidia.com \
--cc=jiaqiyan@google.com \
--cc=joey.gouly@arm.com \
--cc=jthoughton@google.com \
--cc=kvm@vger.kernel.org \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=maz@kernel.org \
--cc=oliver.upton@linux.dev \
--cc=pbonzini@redhat.com \
--cc=rananta@google.com \
--cc=shuah@kernel.org \
--cc=suzuki.poulose@arm.com \
--cc=vsethi@nvidia.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
all inboxes | Powered by JetHome®