On Mon, Feb 01, 2016 at 09:16:02PM +0530, Aneesh Kumar K.V wrote:

Jerome Glisse [off-list ref] writes:

quoted

Hi,

I would like to attend LSF/MM this year to discuss about HMM
(Heterogeneous Memory Manager) and more generaly all topics
related to GPU and heterogeneous memory architecture (including
persistent memory).

I want to discuss how to move forward with HMM merging and i
hope that by MM summit time i will be able to share more
informations publicly on devices which rely on HMM.

I mentioned in my request to attend mail, I would like to attend this
discussion. I am wondering whether we can split the series further to
mmu_notifier bits and then the page table mirroring bits. Can the mmu notifier
changes go in early so that we can merge the page table mirroring later ?

Well the mmu_notifier bit can be upstream on their own but they would
not useful. Maybe on KVM side i need to investigate.

Can be page table mirroring bits be built as a kernel module ?

Well i am not sure this is a good idea. Memory migration requires to
hook up into page fault code path and it relies on the mirrored page
table to service fault on memory that is migrated.

Jerome

--
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>