On Thu, Feb 15, 2024 at 10:31:55AM +0000, Ryan Roberts wrote: > Since set_ptes() was introduced, set_pte_at() has been implemented as a > generic macro around set_ptes(..., 1). So this change should continue to > generate the same code. However, making this change prepares us for the > transparent contpte support. It means we can reroute set_ptes() to > __set_ptes(). Since set_pte_at() is a generic macro, there will be no > equivalent __set_pte_at() to reroute to. > > Note that a couple of calls to set_pte_at() remain in the arch code. > This is intentional, since those call sites are acting on behalf of > core-mm and should continue to call into the public set_ptes() rather > than the arch-private __set_ptes(). > > Tested-by: John Hubbard <jhubbard@xxxxxxxxxx> > Signed-off-by: Ryan Roberts <ryan.roberts@xxxxxxx> Acked-by: Catalin Marinas <catalin.marinas@xxxxxxx>
