diff options
| author | Stefano Stabellini <[email protected]> | 2022-03-04 15:22:54 -0800 |
|---|---|---|
| committer | Christoph Hellwig <[email protected]> | 2022-04-18 07:21:09 +0200 |
| commit | 9bbe7a7fc126e3d14fefa4b035854aba080926d9 (patch) | |
| tree | 000bf5738a511fffce0fb0d3d6f3b335c4e344a7 /scripts/bpf_doc.py | |
| parent | 0d5ffd9a256d8995764f9d4a35a8c3917839d169 (diff) | |
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 <[email protected]>
Signed-off-by: Christoph Hellwig <[email protected]>
Reviewed-by: Konrad Rzeszutek Wilk <[email protected]>
Diffstat (limited to 'scripts/bpf_doc.py')
0 files changed, 0 insertions, 0 deletions