* Mel Gorman <[email protected]> wrote:
> > Would be nice if you gave me all the specific SHA1 tags of
> > sched/core that are required for the fix. We can certainly use a
> > range to make it all safer to apply.
>
> Of course. The range of the relevant commits in tip/sched/core is
> ca4be374c5c0ab3d8b84fb2861d663216281e6ac..778ec5247bb79815af12434980164334fb94cc9e
>
> 904f64a376e663cd459fb7aec4f12e14c39c24b6 mm: numa: Document automatic NUMA
> balancing sysctls
> 1d649bccc8c1370e402b85e1d345ad24f3f0d1b5 sched, numa: Comment fixlets
> f961cab8d55d55d6abc0df08ce2abec8ab56f2c8 mm: numa: Do not account for a
> hinting fault if we raced
> 6f2a15fc1df62af3ba3be327877b7e53cb16e878 mm: Wait for THP migrations to
> complete during NUMA hinting faults
> 4ee547f994c633f2607d222e2c6385b6fe5f07d8 mm: Prevent parallel splits during
> THP migration
> dd83227f0d93fb37d7621a24e8465b13b437faa6 mm: numa: Sanitize task_numa_fault()
> callsites
> efeeacf7b94babff85da7e468fc5450fdfab0900 mm: Close races between THP
> migration and PMD numa clearing
> 778ec5247bb79815af12434980164334fb94cc9e mm: Account for a THP NUMA hinting
> update as one PTE update
These commits don't exist in -tip :-/
Some of these don't even exist as patch titles under different
sha1's - such as "sched, numa: Comment fixlets".
So I'm really confused about what to pick up. What tree are you
looking at?
-tip is at:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
Thanks,
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
