On Mon, Feb 28, 2022 at 10:32:54AM +0000, Robin Murphy wrote: > Is it even possible to hit this case now? From a quick look, all the > architectures defining HIGHMEM either have an explicit dependency on MMU or > don't allow deselecting it anyway (plus I don't see how HIGHMEM && !MMU > could work in general), so I'm pretty sure this whole chunk should go away > now. > > With that (or if there *is* some subtle wacky case where PageHighmem() can > actually return true for !MMU, a comment to remind us in future),
No, you're right - I don't think we can support highmem on !CONFIG_MMU. _______________________________________________ iommu mailing list [email protected] https://lists.linuxfoundation.org/mailman/listinfo/iommu
