summaryrefslogtreecommitdiffstats
path: root/drivers/xen/dbgp.c
diff options
context:
space:
mode:
authorJulien Grall <julien.grall@citrix.com>2015-09-09 16:18:45 +0200
committerDavid Vrabel <david.vrabel@citrix.com>2015-10-23 15:20:43 +0200
commit9435cce87950d805e6c8315410f2cb8ff6b2c6a2 (patch)
tree8d7dbbe5e1ce9ccffcdfda949d0b084ae720997d /drivers/xen/dbgp.c
parentxen/swiotlb: Pass addresses rather than frame numbers to xen_arch_need_swiotlb (diff)
downloadlinux-9435cce87950d805e6c8315410f2cb8ff6b2c6a2.tar.xz
linux-9435cce87950d805e6c8315410f2cb8ff6b2c6a2.zip
xen/swiotlb: Add support for 64KB page granularity
Swiotlb is used on ARM64 to support DMA on platform where devices are not protected by an SMMU. Furthermore it's only enabled for DOM0. While Xen is always using 4KB page granularity in the stage-2 page table, Linux ARM64 may either use 4KB or 64KB. This means that a Linux page can be spanned accross multiple Xen page. The Swiotlb code has to validate that the buffer used for DMA is physically contiguous in the memory. As a Linux page can't be shared between local memory and foreign page by design (the balloon code always removing entirely a Linux page), the changes in the code are very minimal because we only need to check the first Xen PFN. Note that it may be possible to optimize the function check_page_physically_contiguous to avoid looping over every Xen PFN for local memory. Although I will let this optimization for a follow-up. Signed-off-by: Julien Grall <julien.grall@citrix.com> Reviewed-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com> Signed-off-by: David Vrabel <david.vrabel@citrix.com>
Diffstat (limited to 'drivers/xen/dbgp.c')
0 files changed, 0 insertions, 0 deletions