[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Ryzen 6000 (Mobile)
- To: Dylanger Daly <dylangerdaly@xxxxxxxxxxxxxx>
- From: Jan Beulich <jbeulich@xxxxxxxx>
- Date: Thu, 25 Aug 2022 16:55:38 +0200
- Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=suse.com; dmarc=pass action=none header.from=suse.com; dkim=pass header.d=suse.com; arc=none
- Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=ZuTKIXNqDPf21qQmXvGRzRTOuc2XmKPLghP6ySECl14=; b=X45/loYs2k3OtQTBpIW0MiONjUhVl+uDDC/W+fgYWSOdq7djPwjoo23CEjv+b9zdwsJ2fpfXdOJrBXNZeYa5F4zM2f8I+jnWEJ+AXIs3JW3v+xiU0stZic3D9fJ8bh7oWjRhyYm/JnAzLCAlhGQ2wbZVaMp45yAOJ4gtDIiG1a4g9EI0GgaCeO9vSh0d/SHy3YqCJhmEej4wYgGQ2b6vyImNleJv38Px0Asa+SMJm5XieGMwj3ZfPQ+2xJszyz1AVZT4W5Ssv/XLnYYunjGuoTPWnrtVbEXfeaqVByS05+7/H5Vy0EgCWin6IsuExF77zrT4CtV7HmAVIBKQqZdTeA==
- Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=e4xTZ5+GpfW609YWFF5CFdekAeBQvz2TJbuFQOKHwftjMXucBB9gcH1RSLYZOZt//ztX9Obm43q6cwSiakpf3/YNdHIwQi+6JjVYu2YaB1sXKV9GMLcTPvH8LeCqJRpjQti4JG251AdEiUEM0DuvnlyIncVADG/fFTl7go1kITmHR1Wd7LsTDXvRc+665WHK2yfhOUImjFbanjwAT30A/J2nM9a9NZ5R4z0mEMoT+1aThBpDKeaVzkh/ekA4pjTSNZlYtLL5uq4JMIKN/iByT3JKeMFvynH2NLyjQTcTC0khdxcvtEA+PF8Kn+wsioH1WFBA5AMzXnDpP8XVBQgURQ==
- Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=suse.com;
- Cc: xen-devel@xxxxxxxxxxxxxxxxxxxx, Andrew.Cooper3@xxxxxxxxxx
- Delivery-date: Thu, 25 Aug 2022 14:55:53 +0000
- List-id: Xen developer discussion <xen-devel.lists.xenproject.org>
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);
|
