[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <D03NWFQM9XP2.1AWMB9VW98Z98@kernel.org>
Date: Tue, 26 Mar 2024 13:57:37 +0200
From: "Jarkko Sakkinen" <jarkko@...nel.org>
To: "Rick Edgecombe" <rick.p.edgecombe@...el.com>,
<Liam.Howlett@...cle.com>, <akpm@...ux-foundation.org>, <bp@...en8.de>,
<broonie@...nel.org>, <christophe.leroy@...roup.eu>,
<dave.hansen@...ux.intel.com>, <debug@...osinc.com>, <hpa@...or.com>,
<keescook@...omium.org>, <kirill.shutemov@...ux.intel.com>,
<luto@...nel.org>, <mingo@...hat.com>, <peterz@...radead.org>,
<tglx@...utronix.de>, <x86@...nel.org>
Cc: <linux-kernel@...r.kernel.org>, <linux-mm@...ck.org>,
<linux-s390@...r.kernel.org>, <sparclinux@...r.kernel.org>,
<linux-sgx@...r.kernel.org>, <nvdimm@...ts.linux.dev>,
<linux-cxl@...r.kernel.org>, <linux-fsdevel@...r.kernel.org>,
<io-uring@...r.kernel.org>, <bpf@...r.kernel.org>
Subject: Re: [PATCH v4 02/14] mm: Switch mm->get_unmapped_area() to a flag
On Tue Mar 26, 2024 at 4:16 AM EET, Rick Edgecombe wrote:
> The mm_struct contains a function pointer *get_unmapped_area(), which
> is set to either arch_get_unmapped_area() or
> arch_get_unmapped_area_topdown() during the initialization of the mm.
In which conditions which path is used during the initialization of mm
and why is this the case? It is an open claim in the current form.
That would be nice to have documented for the sake of being complete
description. I have zero doubts of the claim being untrue.
BR, Jarkko
Powered by blists - more mailing lists