On 12/4/25 06:25, Anshuman Khandual wrote:
On 03/12/25 1:50 PM, Kevin Brodsky wrote:
On 28/11/2025 14:55, Alexander Gordeev wrote:
+ * in_lazy_mmu_mode() can be used to check whether the lazy MMU mode is
+ * currently enabled.
The in_lazy_mmu_mode() name looks ambiguous to me. When the lazy MMU mode
is paused are we still in lazy MMU mode? The __task_lazy_mmu_mode_active()
implementation suggests we are not, while one could still assume we are,
just paused.
Should in_lazy_mmu_mode() be named e.g. as in_active_lazy_mmu_mode() such
a confusion would not occur in the first place.
I see your point, how about is_lazy_mmu_mode_active()?
Agreed - is_lazy_mmu_mode_active() seems better.
+1, I was scratching my head over this in previous revisions as well.
--
Cheers
David
