On 01/16/2018 01:30 PM, Jerome Glisse wrote: > I want to talk about status of HMM and respective upstream user for > it and also talk about what's next in term of features/improvement > plan (generic page write protection, mmu_notifier, ...). Most likely > short 15-30minutes if mmu_notifier is split into its own topic. > > I want to talk about mmu_notifier, specificaly adding more context > information to mmu_notifier callback (why a notification is happening > reclaim, munmap, migrate, ...). Maybe we can grow this into its own > topic and talk about mmu_notifier and issue with it like OOM or being > able to sleep/take lock ... and improving mitigation. > > People (mmu_notifier probably interest a larger set): > "Anshuman Khandual" <khandual@xxxxxxxxxxxxxxxxxx> > "Balbir Singh" <bsingharora@xxxxxxxxx> > "David Rientjes" <rientjes@xxxxxxxxxx> > "John Hubbard" <jhubbard@xxxxxxxxxx> > "Michal Hocko" <mhocko@xxxxxxxx> > Hi Jerome, Thanks again for including me here. I am very interesting in discussing this, seeing as how we're busy adding HMM support to our driver(s). The teardown cases still concern us, as you know (today's HMM lacks a callback for when the struct mm disappears, for example), but that's really just a subset of the mmu_notifier discussion that you list above. Hope to see you there. thanks, -- John Hubbard NVIDIA -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>
