Hey Po-Hsu, I attempted to get a generic/generic-64k kernel to boot in ec2 and never got it to recognize the root device, so I couldn't reporduce the failure. That said, from what I've read it and what the failed tests report indicates that despite the kernel reporting mmap_min_addr of 32k, the kernel enforces it by pages so on a 64k page system, the actual enforced value will be 64k.
I verified that it didn't trigger with the regular aws arm kernel, but it would be great if you could validate the adjusted test on arm64 + 64k page environment.
Hey Po-Hsu, I attempted to get a generic/generic-64k kernel to boot in ec2 and never got it to recognize the root device, so I couldn't reporduce the failure. That said, from what I've read it and what the failed tests report indicates that despite the kernel reporting mmap_min_addr of 32k, the kernel enforces it by pages so on a 64k page system, the actual enforced value will be 64k.
I have gone ahead and committed a fix to QRT that checks for whether CONFIG_ ARM64_64K_ PAGES is enabled and keeps the expected 64k enforced value if so: https:/ /git.launchpad. net/qa- regression- testing/ commit/ ?id=d56f3347a1f 69c06be638ca6b6 917083143ce5a4
I verified that it didn't trigger with the regular aws arm kernel, but it would be great if you could validate the adjusted test on arm64 + 64k page environment.
Thanks!