linux.git/include/xen, branch v5.4-rc1

swiotlb-xen: simplify cache maintainance

2019-09-11T10:43:27+00:00

Now that we know we always have the dma-noncoherent.h helpers available
if we are on an architecture with support for non-coherent devices,
we can just call them directly, and remove the calls to the dma-direct
routines, including the fact that we call the dma_direct_map_page
routines but ignore the value returned from it.  Instead we now have
Xen wrappers for the arch_sync_dma_for_{device,cpu} helpers that call
the special Xen versions of those routines for foreign pages.

Note that the new helpers get the physical address passed in addition
to the dma address to avoid another translation for the local cache
maintainance.  The pfn_valid checks remain on the dma address as in
the old code, even if that looks a little funny.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Boris Ostrovsky 
Reviewed-by: Stefano Stabellini 
Acked-by: Konrad Rzeszutek Wilk

swiotlb-xen: use the same foreign page check everywhere

2019-09-11T10:43:27+00:00

xen_dma_map_page uses a different and more complicated check for foreign
pages than the other three cache maintainance helpers.  Switch it to the
simpler pfn_valid method a well, and document the scheme with a single
improved comment in xen_dma_map_page.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Stefano Stabellini

xen/arm: remove xen_dma_ops

2019-09-11T10:43:26+00:00

arm and arm64 can just use xen_swiotlb_dma_ops directly like x86, no
need for a pointer indirection.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Julien Grall 
Reviewed-by: Stefano Stabellini

xen/arm: consolidate page-coherent.h

2019-09-11T10:43:22+00:00

Shared the duplicate arm/arm64 code in include/xen/arm/page-coherent.h.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Stefano Stabellini

xen: avoid link error on ARM

2019-07-31T06:14:12+00:00

Building the privcmd code as a loadable module on ARM, we get
a link error due to the private cache management functions:

ERROR: "__sync_icache_dcache" [drivers/xen/xen-privcmd.ko] undefined!

Move the code into a new that is always built in when Xen is enabled,
as suggested by Juergen Gross and Boris Ostrovsky.

Signed-off-by: Arnd Bergmann 
Reviewed-by: Stefano Stabellini 
Signed-off-by: Juergen Gross

xen: remove tmem driver

2019-07-17T06:09:58+00:00

The Xen tmem (transcendent memory) driver can be removed, as the
related Xen hypervisor feature never made it past the "experimental"
state and will be removed in future Xen versions (>= 4.13).

The xen-selfballoon driver depends on tmem, so it can be removed, too.

Signed-off-by: Juergen Gross 
Acked-by: Boris Ostrovsky 
Signed-off-by: Juergen Gross

xen/events: fix binding user event channels to cpus

2019-07-17T06:09:57+00:00

When binding an interdomain event channel to a vcpu via
IOCTL_EVTCHN_BIND_INTERDOMAIN not only the event channel needs to be
bound, but the affinity of the associated IRQi must be changed, too.
Otherwise the IRQ and the event channel won't be moved to another vcpu
in case the original vcpu they were bound to is going offline.

Cc:  # 4.13
Fixes: c48f64ab472389df ("xen-evtchn: Bind dyn evtchn:qemu-dm interrupt to next online VCPU")
Signed-off-by: Juergen Gross 
Reviewed-by: Boris Ostrovsky 
Signed-off-by: Juergen Gross

block: pass page to xen_biovec_phys_mergeable

2019-04-01T18:11:13+00:00

xen_biovec_phys_mergeable() only needs .bv_page of the 2nd bio bvec
for checking if the two bvecs can be merged, so pass page to
xen_biovec_phys_mergeable() directly.

No function change.

Cc: ris Ostrovsky 
Cc: Juergen Gross 
Cc: xen-devel@lists.xenproject.org
Cc: Omar Sandoval 
Cc: Christoph Hellwig 
Reviewed-by: Christoph Hellwig 
Reviewed-by: Boris Ostrovsky 
Signed-off-by: Ming Lei 
Signed-off-by: Jens Axboe

x86/xen: dont add memory above max allowed allocation

2019-02-18T05:52:51+00:00

Don't allow memory to be added above the allowed maximum allocation
limit set by Xen.

Trying to do so would result in cases like the following:

[  584.559652] ------------[ cut here ]------------
[  584.564897] WARNING: CPU: 2 PID: 1 at ../arch/x86/xen/multicalls.c:129 xen_alloc_pte+0x1c7/0x390()
[  584.575151] Modules linked in:
[  584.578643] Supported: Yes
[  584.581750] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 4.4.120-92.70-default #1
[  584.590000] Hardware name: Cisco Systems Inc UCSC-C460-M4/UCSC-C460-M4, BIOS C460M4.4.0.1b.0.0629181419 06/29/2018
[  584.601862]  0000000000000000 ffffffff813175a0 0000000000000000 ffffffff8184777c
[  584.610200]  ffffffff8107f4e1 ffff880487eb7000 ffff8801862b79c0 ffff88048608d290
[  584.618537]  0000000000487eb7 ffffea0000000201 ffffffff81009de7 ffffffff81068561
[  584.626876] Call Trace:
[  584.629699]  [] dump_trace+0x59/0x340
[  584.635645]  [] show_stack_log_lvl+0xea/0x170
[  584.642391]  [] show_stack+0x21/0x40
[  584.648238]  [] dump_stack+0x5c/0x7c
[  584.654085]  [] warn_slowpath_common+0x81/0xb0
[  584.660932]  [] xen_alloc_pte+0x1c7/0x390
[  584.667289]  [] pmd_populate_kernel.constprop.6+0x40/0x80
[  584.675241]  [] phys_pmd_init+0x210/0x255
[  584.681587]  [] phys_pud_init+0x1da/0x247
[  584.687931]  [] kernel_physical_mapping_init+0xf5/0x1d4
[  584.695682]  [] init_memory_mapping+0x18d/0x380
[  584.702631]  [] arch_add_memory+0x59/0xf0

Signed-off-by: Juergen Gross 
Reviewed-by: Boris Ostrovsky 
Signed-off-by: Juergen Gross

arm64/xen: fix xen-swiotlb cache flushing

2019-01-23T21:14:56+00:00

Xen-swiotlb hooks into the arm/arm64 arch code through a copy of the DMA
DMA mapping operations stored in the struct device arch data.

Switching arm64 to use the direct calls for the merged DMA direct /
swiotlb code broke this scheme.  Replace the indirect calls with
direct-calls in xen-swiotlb as well to fix this problem.

Fixes: 356da6d0cde3 ("dma-mapping: bypass indirect calls for dma-direct")
Reported-by: Julien Grall 
Signed-off-by: Christoph Hellwig 
Reviewed-by: Stefano Stabellini