On 2026-01-23 at 08:41 +1100, Andrew Morton <[email protected]> wrote... > On Thu, 22 Jan 2026 20:10:44 +1100 Balbir Singh <[email protected]> wrote: > > > >> - Intel has demonstrated that this works and is still getting blocked. > > >> > > >> - This entire thread is about a fixes patch for large device pages. > > >> Changing prep_compound_page is completely out of scope for a fixes > > >> patch, and honestly so is most of the rest of what’s being proposed. > > > > > > FWIW I'm ok if this lands as a fix patch, and perceived the discussion to > > > be > > > about how refactor things more properly afterwards, going forward. > > > > > > > I've said the same thing and I concur, we can use the patch as-is and > > change this to set the relevant identified fields after 6.19 > > So the plan is to add this patch to 6.19-rc and take another look at > patches [2-5] during next -rc cycle?
I'm ok with this as a a quick fix, and happy to take a look at cleaning this up in the next cycle or two as it's been on my TODO list for a while anyway. > I think the plan is to take Matthew's work via the DRM tree? But if people > want me to patchbunny this fix then please lmk. > > I presently have > > Signed-off-by: Matthew Brost <[email protected]> > Signed-off-by: Francois Dugast <[email protected]> > Acked-by: Felix Kuehling <[email protected]> > Reviewed-by: Balbir Singh <[email protected]> > > If people wish to add to this then please do so. > > I'll restore this patch into mm.git's hotfix branch (and hence > linux-next) because testing.
