Re: [PATCH v5 01/25] mm: Clarify the spec for set_ptes()

2024-02-12 Thread David Hildenbrand
On 02.02.24 09:07, Ryan Roberts wrote: set_ptes() spec implies that it can only be used to set a present pte because it interprets the PFN field to increment it. However, set_pte_at() has been implemented on top of set_ptes() since set_ptes() was introduced, and set_pte_at() allows setting a pte

[PATCH v5 01/25] mm: Clarify the spec for set_ptes()

2024-02-02 Thread Ryan Roberts
set_ptes() spec implies that it can only be used to set a present pte because it interprets the PFN field to increment it. However, set_pte_at() has been implemented on top of set_ptes() since set_ptes() was introduced, and set_pte_at() allows setting a pte to a not-present state. So clarify the sp