From: "Jérôme Glisse" <j.glisse@gmail.com> To: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: mgorman@suse.de, hpa@zytor.com, peterz@infraread.org, aarcange@redhat.com, riel@redhat.com, jweiner@redhat.com, torvalds@linux-foundation.org, Mark Hairgrove <mhairgrove@nvidia.com>, Jatin Kumar <jakumar@nvidia.com>, Subhash Gutti <sgutti@nvidia.com>, Lucien Dunning <ldunning@nvidia.com>, Cameron Buschardt <cabuschardt@nvidia.com>, Arvind Gopalakrishnan <arvindg@nvidia.com>, John Hubbard <jhubbard@nvidia.com>, Sherry Cheung <SCheung@nvidia.com>, Duncan Poole <dpoole@nvidia.com>, Oded Gabbay <Oded.Gabbay@amd.com>, Alexander Deucher <Alexander.Deucher@amd.com>, Andrew Lewycky <Andrew.Lewycky@amd.com> Subject: mm preparatory patches for HMM and IOMMUv2 Date: Fri, 27 Jun 2014 22:00:18 -0400 [thread overview] Message-ID: <1403920822-14488-1-git-send-email-j.glisse@gmail.com> (raw) Andrew so here are a set of mm patch that do some ground modification to core mm code. They apply on top of today's linux-next and they pass checkpatch.pl with flying color (except patch 4 but i did not wanted to be a nazi about 80 char line). Patch 1 is the mmput notifier call chain we discussed with AMD. Patch 2, 3 and 4 are so far only useful to HMM but i am discussing with AMD and i believe it will be useful to them to (in the context of IOMMUv2). Patch 2 allows to differentiate page unmap for vmscan reason or for poisoning. Patch 3 associate mmu_notifier with an event type allowing to take different code path inside mmu_notifier callback depending on what is currently happening to the cpu page table. There is no functional change, it just add a new argument to the various mmu_notifier calls and callback. Patch 4 pass along the vma into which the range invalidation is happening. There is few functional changes in place where mmu_notifier_range_invalidate_start/end used [0, -1] as range, instead now those place call the notifier once for each vma. This might prove to add unwanted overhead hence why i did it as a separate patch. I did not include the core hmm patch but i intend to send a v4 next week. So i really would like to see those included for next release. As usual comments welcome. Cheers, Jérôme Glisse
WARNING: multiple messages have this Message-ID (diff)
From: "Jérôme Glisse" <j.glisse@gmail.com> To: akpm@linux-foundation.org, linux-mm@kvack.org, linux-kernel@vger.kernel.org Cc: mgorman@suse.de, hpa@zytor.com, peterz@infraread.org, aarcange@redhat.com, riel@redhat.com, jweiner@redhat.com, torvalds@linux-foundation.org, Mark Hairgrove <mhairgrove@nvidia.com>, Jatin Kumar <jakumar@nvidia.com>, Subhash Gutti <sgutti@nvidia.com>, Lucien Dunning <ldunning@nvidia.com>, Cameron Buschardt <cabuschardt@nvidia.com>, Arvind Gopalakrishnan <arvindg@nvidia.com>, John Hubbard <jhubbard@nvidia.com>, Sherry Cheung <SCheung@nvidia.com>, Duncan Poole <dpoole@nvidia.com>, Oded Gabbay <Oded.Gabbay@amd.com>, Alexander Deucher <Alexander.Deucher@amd.com>, Andrew Lewycky <Andrew.Lewycky@amd.com> Subject: mm preparatory patches for HMM and IOMMUv2 Date: Fri, 27 Jun 2014 22:00:18 -0400 [thread overview] Message-ID: <1403920822-14488-1-git-send-email-j.glisse@gmail.com> (raw) Andrew so here are a set of mm patch that do some ground modification to core mm code. They apply on top of today's linux-next and they pass checkpatch.pl with flying color (except patch 4 but i did not wanted to be a nazi about 80 char line). Patch 1 is the mmput notifier call chain we discussed with AMD. Patch 2, 3 and 4 are so far only useful to HMM but i am discussing with AMD and i believe it will be useful to them to (in the context of IOMMUv2). Patch 2 allows to differentiate page unmap for vmscan reason or for poisoning. Patch 3 associate mmu_notifier with an event type allowing to take different code path inside mmu_notifier callback depending on what is currently happening to the cpu page table. There is no functional change, it just add a new argument to the various mmu_notifier calls and callback. Patch 4 pass along the vma into which the range invalidation is happening. There is few functional changes in place where mmu_notifier_range_invalidate_start/end used [0, -1] as range, instead now those place call the notifier once for each vma. This might prove to add unwanted overhead hence why i did it as a separate patch. I did not include the core hmm patch but i intend to send a v4 next week. So i really would like to see those included for next release. As usual comments welcome. Cheers, JA(C)rA'me Glisse -- 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>
next reply other threads:[~2014-06-28 2:00 UTC|newest] Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-06-28 2:00 Jérôme Glisse [this message] 2014-06-28 2:00 ` mm preparatory patches for HMM and IOMMUv2 Jérôme Glisse 2014-06-28 2:00 ` [PATCH 1/6] mmput: use notifier chain to call subsystem exit handler Jérôme Glisse 2014-06-28 2:00 ` Jérôme Glisse 2014-06-30 3:49 ` John Hubbard 2014-06-30 3:49 ` John Hubbard 2014-06-30 15:07 ` Jerome Glisse 2014-06-30 15:07 ` Jerome Glisse 2014-06-30 14:41 ` Gabbay, Oded 2014-06-30 14:41 ` Gabbay, Oded 2014-06-30 15:06 ` Jerome Glisse 2014-06-30 15:06 ` Jerome Glisse [not found] ` <019CCE693E457142B37B791721487FD91806B836-0nO7ALo/ziwxlywnonMhLEEOCMrvLtNR@public.gmane.org> 2014-06-30 15:40 ` Joerg Roedel 2014-06-30 16:06 ` Jerome Glisse 2014-06-30 16:06 ` Jerome Glisse 2014-06-30 18:16 ` Joerg Roedel 2014-06-30 18:16 ` Joerg Roedel 2014-06-30 18:35 ` Jerome Glisse 2014-06-30 18:35 ` Jerome Glisse 2014-06-30 18:57 ` Lewycky, Andrew 2014-06-30 18:57 ` Lewycky, Andrew 2014-07-01 9:41 ` Joerg Roedel 2014-07-01 9:41 ` Joerg Roedel [not found] ` <20140630183556.GB3280-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2014-07-01 9:15 ` Joerg Roedel 2014-07-01 9:29 ` Gabbay, Oded 2014-07-01 9:29 ` Gabbay, Oded [not found] ` <019CCE693E457142B37B791721487FD91806DD8B-0nO7ALo/ziwxlywnonMhLEEOCMrvLtNR@public.gmane.org> 2014-07-01 11:00 ` Joerg Roedel 2014-07-01 19:33 ` Jerome Glisse 2014-07-01 19:33 ` Jerome Glisse [not found] ` <20140701193343.GB3322-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2014-07-01 21:06 ` Joerg Roedel 2014-07-01 21:32 ` Jerome Glisse 2014-07-01 21:32 ` Jerome Glisse 2014-07-03 18:30 ` Jerome Glisse 2014-07-03 18:30 ` Jerome Glisse [not found] ` <20140703183024.GA3306-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> 2014-07-03 23:15 ` Joerg Roedel 2014-07-04 0:03 ` Jerome Glisse 2014-07-04 0:03 ` Jerome Glisse 2014-07-06 19:25 ` Gabbay, Oded 2014-07-06 19:25 ` Gabbay, Oded 2014-07-07 10:11 ` joro 2014-07-07 10:11 ` joro 2014-07-07 10:36 ` Oded Gabbay 2014-07-07 10:36 ` Oded Gabbay 2014-07-07 10:43 ` Oded Gabbay 2014-07-07 10:43 ` Oded Gabbay [not found] ` <1404729783.31606.1.camel-OrheeFI7RUaGvNAqNQFwiPZ4XP/Yx64J@public.gmane.org> 2014-07-08 8:00 ` joro-zLv9SwRftAIdnm+yROfE0A 2014-07-08 17:03 ` Jerome Glisse 2014-07-08 17:03 ` Jerome Glisse 2015-10-11 19:03 ` David Woodhouse 2015-10-11 19:03 ` David Woodhouse 2015-10-12 17:41 ` Jerome Glisse 2015-10-12 17:41 ` Jerome Glisse 2015-10-12 17:41 ` Jerome Glisse 2015-11-20 15:45 ` David Woodhouse 2015-11-20 15:45 ` David Woodhouse 2014-06-30 15:37 ` Joerg Roedel 2014-06-28 2:00 ` [PATCH 2/6] mm: differentiate unmap for vmscan from other unmap Jérôme Glisse 2014-06-28 2:00 ` Jérôme Glisse 2014-06-30 3:58 ` John Hubbard 2014-06-30 3:58 ` John Hubbard 2014-06-30 15:58 ` Jerome Glisse 2014-06-30 15:58 ` Jerome Glisse 2014-06-28 2:00 ` [PATCH 3/6] mmu_notifier: add event information to address invalidation v2 Jérôme Glisse 2014-06-28 2:00 ` Jérôme Glisse 2014-06-30 5:22 ` John Hubbard 2014-06-30 5:22 ` John Hubbard 2014-06-30 15:57 ` Jerome Glisse 2014-06-30 15:57 ` Jerome Glisse 2014-07-01 1:57 ` Linus Torvalds 2014-06-28 2:00 ` [PATCH 4/6] mmu_notifier: pass through vma to invalidate_range and invalidate_page Jérôme Glisse 2014-06-28 2:00 ` Jérôme Glisse 2014-06-30 3:29 ` John Hubbard 2014-06-30 3:29 ` John Hubbard 2014-06-30 16:00 ` Jerome Glisse 2014-06-30 16:00 ` Jerome Glisse 2014-07-01 2:04 ` Linus Torvalds
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=1403920822-14488-1-git-send-email-j.glisse@gmail.com \ --to=j.glisse@gmail.com \ --cc=Alexander.Deucher@amd.com \ --cc=Andrew.Lewycky@amd.com \ --cc=Oded.Gabbay@amd.com \ --cc=SCheung@nvidia.com \ --cc=aarcange@redhat.com \ --cc=akpm@linux-foundation.org \ --cc=arvindg@nvidia.com \ --cc=cabuschardt@nvidia.com \ --cc=dpoole@nvidia.com \ --cc=hpa@zytor.com \ --cc=jakumar@nvidia.com \ --cc=jhubbard@nvidia.com \ --cc=jweiner@redhat.com \ --cc=ldunning@nvidia.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=mgorman@suse.de \ --cc=mhairgrove@nvidia.com \ --cc=peterz@infraread.org \ --cc=riel@redhat.com \ --cc=sgutti@nvidia.com \ --cc=torvalds@linux-foundation.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.