On Thu, Dec 11, 2025 at 10:11 AM Sebastian Ott sebott@redhat.com wrote:
On Thu, 11 Dec 2025, Jiaqi Yan wrote:
CONFIGs seem alright to me. Do you boot kernel with cmdline options like "default_hugepagesz=1G hugepagesz=1G hugepages=64", or dynamically set up huge pages via "echo 64 > /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages"?
Neither of these. When I do the test is skipped: # echo 64 > /sys/kernel/mm/hugepages/hugepages-1048576kB/nr_hugepages # ./arm64/sea_to_user 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=0x80241234bad ok 1 # SKIP EINJ module probably not loaded?sh: line 1: /sys/kernel/debug/apei/einj/error_type: No such file or directory Bail out! Failed to write EINJ entry: No such file or directory (2)
Looks like EINJ is not available on your test machine. You will need to check several things: 1. does your firmware have EINJ support? kernel should log something like "ACPI: EINJ populated" at boot time, but it doesn't guarantee the EINJ support, just suggesting it may support. 2. if you are sure about the firmware, did you build kernel with CONFIG_ACPI_APEI_EINJ=m? 3. if CONFIG_ACPI_APEI_EINJ=m, please also "modprobe einj". If modprobe failed or /sys/kernel/debug/apei/einj/error_type still doesn't show up, firmware probably doesn't support EINJ at all.
I will probably add more comments at the top of the file to clarify things.
# 1 skipped test(s) detected. Consider enabling relevant config options to improve coverage. # Planned tests != run tests (0 != 1) # Totals: pass:0 fail:0 xfail:0 xpass:0 skip:1 error:0