All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Beulich <jbeulich@suse.com>
To: Dylanger Daly <dylangerdaly@protonmail.com>
Cc: xen-devel@lists.xenproject.org, Andrew.Cooper3@citrix.com
Subject: Re: Ryzen 6000 (Mobile)
Date: Thu, 25 Aug 2022 16:55:38 +0200	[thread overview]
Message-ID: <941ccb01-adf6-d2ef-9a8a-ea8fdfe69ceb@suse.com> (raw)
In-Reply-To: <2dHPPtixTlkUXYEzNPFRI4ezKHSe1A2VaThMjBpd1aM3NFkZQuyRdfmNWCigm1oXfdKhOwDJGoPBBIMLYtYhQlENV2eFVZ0G9EMOMj5e6UE=@protonmail.com>

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);



  reply	other threads:[~2022-08-25 14:56 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-18 23:04 Ryzen 6000 (Mobile) Dylanger Daly
2022-07-19  6:29 ` Jan Beulich
2022-07-19  6:47   ` Dylanger Daly
2022-07-19  6:58     ` Jan Beulich
2022-07-19  6:50   ` Dylanger Daly
2022-07-19  9:34 ` Andrew Cooper
2022-07-20  0:33   ` Dylanger Daly
2022-07-20  8:11     ` Jan Beulich
2022-07-20  8:13       ` Jan Beulich
2022-08-15 11:07         ` Dylanger Daly
2022-08-15 11:30           ` Jan Beulich
2022-08-15 11:50             ` Dylanger Daly
2022-08-15 11:55               ` Jan Beulich
2022-08-15 12:03           ` Andrew Cooper
2022-08-15 15:39             ` Dylanger Daly
2022-08-15 16:19               ` Jan Beulich
2022-08-15 16:54                 ` Dylanger Daly
2022-08-16  6:17                   ` Jan Beulich
2022-08-16  8:34                     ` Dylanger Daly
2022-08-16  8:59                       ` Jan Beulich
2022-08-16  9:19                         ` Dylanger Daly
2022-08-16  9:30                           ` Jan Beulich
2022-08-16 11:22                   ` Jan Beulich
2022-08-24 18:15                     ` Dylanger Daly
2022-08-25  8:35                       ` Jan Beulich
2022-08-25 11:10                         ` Dylanger Daly
2022-08-25 14:55                           ` Jan Beulich [this message]
2022-08-29 15:26                             ` Dylanger Daly
2022-09-06 10:52                               ` Jan Beulich
2022-09-06 11:45                                 ` Dylanger Daly
2022-08-31 22:12                             ` Dylanger Daly
2022-09-06 10:50                               ` Jan Beulich
2022-09-03 15:59                             ` Dylanger Daly
2022-09-05 20:44                             ` Dylanger Daly
     [not found]                             ` <6JMvOsjmpWkAsnm6AXzNsjtj5_jy5vG_vG_PwTyDzX0z1buoX89r5UEpSGKf-H7CTBtg9gNlq4Icy7Q9OIDjfrxp2AqNMXbyKTCD0y_d0Hc=@protonmail.com>
2022-09-06 11:51                               ` Jan Beulich

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=941ccb01-adf6-d2ef-9a8a-ea8fdfe69ceb@suse.com \
    --to=jbeulich@suse.com \
    --cc=Andrew.Cooper3@citrix.com \
    --cc=dylangerdaly@protonmail.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.