From: "Roger Pau Monné" <roger.pau@citrix.com>
To: "Lira, Victor M" <VictorM.Lira@amd.com>
Cc: Jason Andryuk <jason.andryuk@amd.com>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org,
Andrew Cooper <andrew.cooper3@citrix.com>,
Jan Beulich <jbeulich@suse.com>,
Xenia.Ragiadakou@amd.com, Alejandro.GarciaVallejo@amd.com
Subject: Re: [RFC] xen/x86: allow overlaps with non-RAM regions
Date: Thu, 24 Apr 2025 09:59:00 +0200 [thread overview]
Message-ID: <aAnvRMgJxAskbCtE@macbook.lan> (raw)
In-Reply-To: <ce06ec74-1a73-4a02-87fc-3e829399cc77@amd.com>
On Wed, Apr 23, 2025 at 04:51:16PM -0700, Lira, Victor M wrote:
> [ 4.570354] Intel(R) 2.5G Ethernet Linux Driver
>
> [ 4.579535] Copyright(c) 2018 Intel Corporation.
>
> [ 4.588898] sky2: driver version 1.30
>
> (XEN) [ 21.644361] d0v3 unable to fixup memory read from 0xfe91000c size 4: -1
This fault is unexpected, according to the identity mappings done at
domain build time:
d0: identity mappings for IOMMU:
[00000000a0, 00000000ff] RW
[0000009bff, 0000009fff] RW
[00000cabc9, 00000cc14c] RW
[00000cc389, 00000cc389] RW
[00000cc70a, 00000cd1fe] RW
[00000ce000, 00000cffff] RW
[00000fd000, 00000fd2ff] RW
The page at 0xfe910 should be covered by the last range above. I
think we have a bug somewhere that unexpectedly unmaps that address.
Can you try the Xen patch below and paste the output? It should print
p2m modifications of the 0xfe910 gfn, so we can spot who/when removes
that mapping.
Thanks, Roger.
---
diff --git a/xen/arch/x86/mm/p2m-pt.c b/xen/arch/x86/mm/p2m-pt.c
index 666abd46be16..c4bb2cb01422 100644
--- a/xen/arch/x86/mm/p2m-pt.c
+++ b/xen/arch/x86/mm/p2m-pt.c
@@ -591,6 +591,14 @@ p2m_pt_set_entry(struct p2m_domain *p2m, gfn_t gfn_, mfn_t mfn,
unsigned int flags, iommu_old_flags = 0;
unsigned long old_mfn = mfn_x(INVALID_MFN);
+ if ( is_hardware_domain(d) &&
+ 0xfe910 >= gfn && 0xfe910 < gfn + (1 << page_order) )
+ {
+ printk("gfn %#lx mfn %#"PRI_mfn" type %u order %u\n",
+ gfn, mfn_x(mfn), p2mt, page_order);
+ WARN();
+ }
+
if ( !sve )
return -EOPNOTSUPP;
next prev parent reply other threads:[~2025-04-24 7:59 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-04 1:01 [RFC] xen/x86: allow overlaps with non-RAM regions Stefano Stabellini
2025-04-04 8:07 ` Jan Beulich
2025-04-10 20:55 ` Jason Andryuk
2025-04-11 7:56 ` Jan Beulich
2025-04-04 10:28 ` Roger Pau Monné
2025-04-10 20:55 ` Jason Andryuk
2025-04-11 7:31 ` Roger Pau Monné
2025-04-11 8:07 ` Jan Beulich
2025-04-11 13:45 ` Jason Andryuk
2025-04-14 8:25 ` Roger Pau Monné
2025-04-23 23:51 ` Lira, Victor M
2025-04-24 7:59 ` Roger Pau Monné [this message]
2025-04-24 10:15 ` Marek Marczykowski-Górecki
2025-04-24 10:48 ` Roger Pau Monné
2025-04-24 21:19 ` Jason Andryuk
2025-04-24 21:38 ` Lira, Victor M
2025-04-25 9:02 ` Roger Pau Monné
2025-04-25 9:19 ` Jan Beulich
2025-04-25 11:09 ` Roger Pau Monné
2025-04-25 16:47 ` Lira, Victor M
2025-05-12 16:16 ` Roger Pau Monné
2025-05-12 17:55 ` Lira, Victor M
2025-05-15 10:19 ` Roger Pau Monné
2025-05-15 16:24 ` Lira, Victor M
2025-04-11 8:15 ` 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=aAnvRMgJxAskbCtE@macbook.lan \
--to=roger.pau@citrix.com \
--cc=Alejandro.GarciaVallejo@amd.com \
--cc=VictorM.Lira@amd.com \
--cc=Xenia.Ragiadakou@amd.com \
--cc=andrew.cooper3@citrix.com \
--cc=jason.andryuk@amd.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--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.