Re: uvm_fault: entering swap code

2020-12-13 Thread Jonathan Matthew
On Sat, Dec 12, 2020 at 10:54:57PM +1000, Jonathan Matthew wrote: > On Thu, Dec 10, 2020 at 10:46:58AM -0300, Martin Pieuchot wrote: > > On 08/12/20(Tue) 22:55, Jonathan Matthew wrote: > > > On Mon, Dec 07, 2020 at 03:15:50PM -0300, Martin Pieuchot wrote: > > > > Getting a page from the fault

Re: uvm_fault: entering swap code

2020-12-12 Thread Jonathan Matthew
On Thu, Dec 10, 2020 at 10:46:58AM -0300, Martin Pieuchot wrote: > On 08/12/20(Tue) 22:55, Jonathan Matthew wrote: > > On Mon, Dec 07, 2020 at 03:15:50PM -0300, Martin Pieuchot wrote: > > > Getting a page from the fault handler might require poking at some > > > swap-related states. > > > > > >

Re: uvm_fault: entering swap code

2020-12-10 Thread Martin Pieuchot
On 08/12/20(Tue) 22:55, Jonathan Matthew wrote: > On Mon, Dec 07, 2020 at 03:15:50PM -0300, Martin Pieuchot wrote: > > Getting a page from the fault handler might require poking at some > > swap-related states. > > > > These are not in the hot-path of the fault handler so for the moment > > just

Re: uvm_fault: entering swap code

2020-12-08 Thread Martin Pieuchot
On 08/12/20(Tue) 22:55, Jonathan Matthew wrote: > On Mon, Dec 07, 2020 at 03:15:50PM -0300, Martin Pieuchot wrote: > > Getting a page from the fault handler might require poking at some > > swap-related states. > > > > These are not in the hot-path of the fault handler so for the moment > > just

Re: uvm_fault: entering swap code

2020-12-08 Thread Jonathan Matthew
On Mon, Dec 07, 2020 at 03:15:50PM -0300, Martin Pieuchot wrote: > Getting a page from the fault handler might require poking at some > swap-related states. > > These are not in the hot-path of the fault handler so for the moment > just assert that the KERNEL_LOCK() is held or grab it if the

uvm_fault: entering swap code

2020-12-07 Thread Martin Pieuchot
Getting a page from the fault handler might require poking at some swap-related states. These are not in the hot-path of the fault handler so for the moment just assert that the KERNEL_LOCK() is held or grab it if the function might be called from an future unlocked path. ok? Index: