diff options
| author | Stefano Stabellini <sstabellini@kernel.org> | 2022-03-05 02:22:54 +0300 |
|---|---|---|
| committer | Christoph Hellwig <hch@lst.de> | 2022-04-18 08:21:09 +0300 |
| commit | 9bbe7a7fc126e3d14fefa4b035854aba080926d9 (patch) | |
| tree | 000bf5738a511fffce0fb0d3d6f3b335c4e344a7 /arch/x86/Kconfig.cpu | |
| parent | 0d5ffd9a256d8995764f9d4a35a8c3917839d169 (diff) | |
| download | linux-9bbe7a7fc126e3d14fefa4b035854aba080926d9.tar.xz | |
arm/xen: don't check for xen_initial_domain() in xen_create_contiguous_region
It used to be that Linux enabled swiotlb-xen when running a dom0 on ARM.
Since f5079a9a2a31 "xen/arm: introduce XENFEAT_direct_mapped and
XENFEAT_not_direct_mapped", Linux detects whether to enable or disable
swiotlb-xen based on the new feature flags: XENFEAT_direct_mapped and
XENFEAT_not_direct_mapped.
However, there is still a leftover xen_initial_domain() check in
xen_create_contiguous_region. Remove the check as
xen_create_contiguous_region is only called by swiotlb-xen during
initialization. If xen_create_contiguous_region is called, we know Linux
is running 1:1 mapped so there is no need for additional checks.
Also update the in-code comment.
Signed-off-by: Stefano Stabellini <stefano.stabellini@xilinx.com>
Signed-off-by: Christoph Hellwig <hch@lst.de>
Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Diffstat (limited to 'arch/x86/Kconfig.cpu')
0 files changed, 0 insertions, 0 deletions