HMM status upstream user what's next, mmu_notifier

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" <[email protected]> "Balbir Singh" <[email protected]> "David Rientjes" <[email protected]> "John Hubbard" <[email protected]> "Michal Hocko" <[email protected]>

Quoted 3 lines

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

I don't think we should consider to push more code to upstream for a nobody-use feature.

AFAIR, Michal also mentioned that HMM need a real user/driver before upstream.
But I haven't seen a workable user/driver version.

Looks like HMM is a custom framework for Nvidia, and Nvidia would not like to open source its driver.
Even if nvidia really use HMM and open sourced its driver, it's probably the only user.
But the HMM framework touched too much core mm code.

Cheers,
Liubo

Quoted 8 lines

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.

Quoted 7 lines

People (mmu_notifier probably interest a larger set):
"Anshuman Khandual" <[email protected]> "Balbir Singh" <[email protected]> "David Rientjes" <[email protected]> "John Hubbard" <[email protected]> "Michal Hocko" <[email protected]>

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to [email protected]. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"[email protected]"> [email protected] </a>

Quoted 3 lines · Jerome Glisse

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

I don't think we should consider to push more code to upstream for a nobody-use feature.

AFAIR, Michal also mentioned that HMM need a real user/driver before upstream. But I haven't seen a workable user/driver version.

Looks like HMM is a custom framework for Nvidia, and Nvidia would not like to open source its driver. Even if nvidia really use HMM and open sourced its driver, it's probably the only user. But the HMM framework touched too much core mm code.

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" <[email protected]> "Balbir Singh" <[email protected]> "David Rientjes" <[email protected]> "John Hubbard" <[email protected]> "Michal Hocko" <[email protected]>

Quoted 5 lines · Liubo(OS Lab)

Quoted 3 lines · Jerome Glisse

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

Quoted 8 lines

I don't think we should consider to push more code to upstream for a nobody-use feature.

AFAIR, Michal also mentioned that HMM need a real user/driver before upstream. But I haven't seen a workable user/driver version.

Looks like HMM is a custom framework for Nvidia, and Nvidia would not like to open source its driver. Even if nvidia really use HMM and open sourced its driver, it's probably the only user. But the HMM framework touched too much core mm code.

So it is not NVidia only, they are other GPU from different company that intend to use HMM, i can't comment any further on timeline.

Regarding NVidia hardware i intend to have the patchset to use HMM inside nouveau ready before summit and post as RFC. Per drm sub-system guideline we can not upstream it until we also have a functional userspace stack and we are also working on that.

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" <[email protected]> "Balbir Singh" <[email protected]> "David Rientjes" <[email protected]> "John Hubbard" <[email protected]> "Michal Hocko" <[email protected]>

Quoted 11 lines · Jerome Glisse

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.

Quoted 6 lines

People (mmu_notifier probably interest a larger set):
"Anshuman Khandual" <[email protected]> "Balbir Singh" <[email protected]> "David Rientjes" <[email protected]> "John Hubbard" <[email protected]> "Michal Hocko" <[email protected]>

I am definitely interested.