2018-01-17 9:19 GMT+08:00 Liubo(OS Lab) <liubo95@huawei.com>:

> On 2018/1/17 5:30, 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
>
> 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.
>

HMM looks suitable for FPGA user case, FPGA and CPU need coherency. ~_~


>
> Cheers,
> Liubo
>
> > 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@linux.vnet.ibm.com>
> >     "Balbir Singh" <bsingharora@gmail.com>
> >     "David Rientjes" <rientjes@google.com>
> >     "John Hubbard" <jhubbard@nvidia.com>
> >     "Michal Hocko" <mhocko@suse.com>
> >
>
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org.  For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>