On 4/25/19 2:45 PM, Mike Rapoport wrote: > After the isolated system call finishes, the mappings created during its > execution are cleared. Yikes. I guess that stops someone from calling write() a bunch of times on every filesystem using every block device driver and all the DM code to get a lot of code/data faulted in. But, it also means not even long-running processes will ever have a chance of behaving anything close to normally. Is this something you think can be rectified or is there something fundamental that would keep SCI page tables from being cached across different invocations of the same syscall?
