On 25.08.2022 13:10, Dylanger Daly wrote:
> Yes please, I have Qubes's Build System setup with sourcehut so I can add
> patches at will, however please be aware Qubes currently uses Xen 4.14.
>
> I'll take a look and see if I can access that location
>
> With the added logging I should be able to trigger the crash and get to the
> bottom of it
Here's the (trivial) patch. It's against out version of 4.14, but I expect
to apply fine. Further logging would likely need to go in the kernel,
since - if my analysis+guessing is right - we wouldn't even see a mapping
attempt in Xen.
Jan
--- sle15sp3.orig/xen/arch/x86/e820.c
+++ sle15sp3/xen/arch/x86/e820.c
@@ -700,3 +700,15 @@ unsigned long __init init_e820(const cha
return find_max_pfn();
}
+
+#include <xen/domain_page.h>//temp
+static int __init ryzen6000_init(void) {//temp
+ if(e820_all_mapped(0x7AF67000, 0x7AF68000, E820_NVS)) {
+ const uint32_t*p = map_domain_page(_mfn(0x7AF67));
+ printk("0x7AF67000: %08x %08x %08x %08x\n", p[0], p[1], p[2], p[3]);
+ printk("0x7AF67010: %08x %08x %08x %08x\n", p[4], p[5], p[6], p[7]);
+ unmap_domain_page(p);
+ }
+ return 0;
+}
+__initcall(ryzen6000_init);
