From: Stefano Stabellini <stefano.stabellini@amd.com>
To: <xen-devel@lists.xenproject.org>
Cc: <sstabellini@kernel.org>, <bertrand.marquis@arm.com>,
<julien@xen.org>, <michal.orzel@amd.com>,
<Volodymyr_Babchuk@epam.com>, Henry Wang <xin.wang2@amd.com>,
Stefano Stabellini <stefano.stabellini@amd.com>
Subject: [PATCH v5 2/9] xen/arm/static-shmem: Static-shmem should be direct-mapped for direct-mapped domains
Date: Wed, 5 Feb 2025 17:08:36 -0800 [thread overview]
Message-ID: <20250206010843.618280-2-stefano.stabellini@amd.com> (raw)
In-Reply-To: <alpine.DEB.2.22.394.2502041807070.9756@ubuntu-linux-20-04-desktop>
From: Henry Wang <xin.wang2@amd.com>
Currently, users are allowed to map static shared memory in a
non-direct-mapped way for direct-mapped domains. This can lead to
clashing of guest memory spaces. Also, the current extended region
finding logic only removes the host physical addresses of the
static shared memory areas for direct-mapped domains, which may be
inconsistent with the guest memory map if users map the static
shared memory in a non-direct-mapped way. This will lead to incorrect
extended region calculation results.
To make things easier, add restriction that static shared memory
should also be direct-mapped for direct-mapped domains. Check the
host physical address to be matched with guest physical address when
parsing the device tree. Document this restriction in the doc.
Signed-off-by: Henry Wang <xin.wang2@amd.com>
Signed-off-by: Stefano Stabellini <stefano.stabellini@amd.com>
Acked-by: Michal Orzel <michal.orzel@amd.com>
---
docs/misc/arm/device-tree/booting.txt | 3 +++
xen/arch/arm/static-shmem.c | 6 ++++++
2 files changed, 9 insertions(+)
diff --git a/docs/misc/arm/device-tree/booting.txt b/docs/misc/arm/device-tree/booting.txt
index 9c881baccc..ff70d44462 100644
--- a/docs/misc/arm/device-tree/booting.txt
+++ b/docs/misc/arm/device-tree/booting.txt
@@ -615,6 +615,9 @@ communication.
Note that if a domain is direct-mapped, i.e. the Dom0 and the Dom0less
DomUs with `direct-map` device tree property, the static shared memory
should also be direct-mapped (host physical address == guest address).
+ Note that if a domain is direct-mapped, i.e. the Dom0 and the Dom0less
+ DomUs with `direct-map` device tree property, the static shared memory
+ should also be direct-mapped (host physical address == guest address).
It shall also meet the following criteria:
1) If the SHM ID matches with an existing region, the address range of the
diff --git a/xen/arch/arm/static-shmem.c b/xen/arch/arm/static-shmem.c
index 8f87154c35..44eeac2a23 100644
--- a/xen/arch/arm/static-shmem.c
+++ b/xen/arch/arm/static-shmem.c
@@ -325,6 +325,12 @@ int __init process_shm(struct domain *d, struct kernel_info *kinfo,
printk("%pd: static shared memory bank not found: '%s'", d, shm_id);
return -ENOENT;
}
+ if ( is_domain_direct_mapped(d) && (pbase != gbase) )
+ {
+ printk("%pd: physical address 0x%"PRIpaddr" and guest address 0x%"PRIpaddr" are not direct-mapped.\n",
+ d, pbase, gbase);
+ return -EINVAL;
+ }
pbase = boot_shm_bank->start;
psize = boot_shm_bank->size;
--
2.25.1
next prev parent reply other threads:[~2025-02-06 1:09 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-06 1:08 [PATCH v5 0/9] Guest XenStore page allocation for 11 Dom0less domUs Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 1/9] automation: upgrade Linux kernel for arm64 tests to 6.6.74 Stefano Stabellini
2025-02-06 7:58 ` Orzel, Michal
2025-02-06 23:12 ` Stefano Stabellini
2025-02-06 1:08 ` Stefano Stabellini [this message]
2025-02-06 8:04 ` [PATCH v5 2/9] xen/arm/static-shmem: Static-shmem should be direct-mapped for direct-mapped domains Orzel, Michal
2025-02-06 23:13 ` Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 3/9] xen/arm: Alloc XenStore page for Dom0less DomUs from hypervisor Stefano Stabellini
2025-02-06 10:20 ` Orzel, Michal
2025-02-07 1:19 ` Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 4/9] tools/init-dom0less: Avoid hardcoding GUEST_MAGIC_BASE Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 5/9] docs/features/dom0less: Update the late XenStore init protocol Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 6/9] automation: add ping test to static-mem test Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 7/9] init-dom0less: allocate xenstore page is not already allocated Stefano Stabellini
2025-02-06 12:37 ` Jan Beulich
2025-02-06 23:14 ` Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 8/9] xen/arm: introduce legacy dom0less option for xenstore allocation Stefano Stabellini
2025-02-06 12:08 ` Orzel, Michal
2025-02-07 1:43 ` Stefano Stabellini
2025-02-06 1:08 ` [PATCH v5 9/9] [DO NOT COMMIT] automation: add one test using an older unpatched Linux kernel Stefano Stabellini
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=20250206010843.618280-2-stefano.stabellini@amd.com \
--to=stefano.stabellini@amd.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=bertrand.marquis@arm.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
--cc=xin.wang2@amd.com \
/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.