diff options
| author | Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com> | 2021-12-09 22:05:34 +0200 |
|---|---|---|
| committer | Juergen Gross <jgross@suse.com> | 2022-01-06 09:53:38 +0100 |
| commit | d1a928eac72962b562162c25baf45ce147e27247 (patch) | |
| tree | 8fc44cbedd4f423cb931b5924932e548dd024625 /include/xen | |
| parent | 9dd060afe2dfd4e3f67b6732fdc681e52cd7cbd9 (diff) | |
| download | linux-d1a928eac72962b562162c25baf45ce147e27247.tar.gz linux-d1a928eac72962b562162c25baf45ce147e27247.tar.bz2 linux-d1a928eac72962b562162c25baf45ce147e27247.zip | |
xen/unpopulated-alloc: Add mechanism to use Xen resource
The main reason of this change is that unpopulated-alloc
code cannot be used in its current form on Arm, but there
is a desire to reuse it to avoid wasting real RAM pages
for the grant/foreign mappings.
The problem is that system "iomem_resource" is used for
the address space allocation, but the really unallocated
space can't be figured out precisely by the domain on Arm
without hypervisor involvement. For example, not all device
I/O regions are known by the time domain starts creating
grant/foreign mappings. And following the advise from
"iomem_resource" we might end up reusing these regions by
a mistake. So, the hypervisor which maintains the P2M for
the domain is in the best position to provide unused regions
of guest physical address space which could be safely used
to create grant/foreign mappings.
Introduce new helper arch_xen_unpopulated_init() which purpose
is to create specific Xen resource based on the memory regions
provided by the hypervisor to be used as unused space for Xen
scratch pages. If arch doesn't define arch_xen_unpopulated_init()
the default "iomem_resource" will be used.
Update the arguments list of allocate_resource() in fill_list()
to always allocate a region from the hotpluggable range
(maximum possible addressable physical memory range for which
the linear mapping could be created). If arch doesn't define
arch_get_mappable_range() the default range (0,-1) will be used.
The behaviour on x86 won't be changed by current patch as both
arch_xen_unpopulated_init() and arch_get_mappable_range()
are not implemented for it.
Also fallback to allocate xenballooned pages (balloon out RAM
pages) if we do not have any suitable resource to work with
(target_resource is invalid) and as the result we won't be able
to provide unpopulated pages on a request.
Signed-off-by: Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>
Link: https://lore.kernel.org/r/1639080336-26573-5-git-send-email-olekstysh@gmail.com
Signed-off-by: Juergen Gross <jgross@suse.com>
Diffstat (limited to 'include/xen')
| -rw-r--r-- | include/xen/xen.h | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/include/xen/xen.h b/include/xen/xen.h index 86c5b37684d9..a99bab817523 100644 --- a/include/xen/xen.h +++ b/include/xen/xen.h @@ -55,6 +55,8 @@ extern u64 xen_saved_max_mem_size; #ifdef CONFIG_XEN_UNPOPULATED_ALLOC int xen_alloc_unpopulated_pages(unsigned int nr_pages, struct page **pages); void xen_free_unpopulated_pages(unsigned int nr_pages, struct page **pages); +#include <linux/ioport.h> +int arch_xen_unpopulated_init(struct resource **res); #else #include <xen/balloon.h> static inline int xen_alloc_unpopulated_pages(unsigned int nr_pages, |