[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220616165413.c35yliaxbxvmwsqw@black.fi.intel.com>
Date: Thu, 16 Jun 2022 19:54:13 +0300
From: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
To: Peter Zijlstra <peterz@...radead.org>
Cc: Andy Lutomirski <luto@...nel.org>,
Rick P Edgecombe <rick.p.edgecombe@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"H.J. Lu" <hjl.tools@...il.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
Dave Hansen <dave.hansen@...ux.intel.com>,
"andreyknvl@...il.com" <andreyknvl@...il.com>,
"kcc@...gle.com" <kcc@...gle.com>, Andi Kleen <ak@...ux.intel.com>,
"dvyukov@...gle.com" <dvyukov@...gle.com>,
the arch/x86 maintainers <x86@...nel.org>,
"ryabinin.a.a@...il.com" <ryabinin.a.a@...il.com>,
"glider@...gle.com" <glider@...gle.com>
Subject: Re: [PATCHv3 6/8] x86/mm: Provide ARCH_GET_UNTAG_MASK and
ARCH_ENABLE_TAGGED_ADDR
On Thu, Jun 16, 2022 at 11:44:59AM +0200, Peter Zijlstra wrote:
> > get_nr_threads() is the wrong thing. Either look at mm->mm_users or
> > find a way to get rid of this restriction entirely.
>
> mm->mm_users should indeed be sufficient here.
Hm. kthread_use_mm() doesn't bump mm_users. Do we care?
--
Kirill A. Shutemov
Powered by blists - more mailing lists