Re: [PATCH v9 00/12] AMD broadcast TLB invalidation

Peter Zijlstra
2025-02-06T14:23:35Z

On Thu, Feb 06, 2025 at 09:16:35AM -0500, Rik van Riel wrote:

> This can result in flush_tlb_mm_range being called
> with a stride_shift for 2MB pages, but a range ending
> on a 4kB aligned (not 2MB aligned) boundary.
>
> Peter, how should we solve this one?

I don't think that's wrong per-se, since all we really need is for end
to be past the end, one byte, one page, or one stride don't matter much.

Anyway, I'm in desperate need of a break, so I'm not quite sure what the
best way forward is.