Received-SPF: pass (google.com: domain of linux-kernel+bounces-24249-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <49231a98-d39f-4920-8d9f-e60aa014f518@zytor.com>
Date: Thu, 11 Jan 2024 18:54:41 -0800
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH 00/45] C++: Convert the kernel to C++
Content-Language: en-US
From: "H. Peter Anvin" <hpa@zytor.com>
To: David Howells <dhowells@redhat.com>, linux-kernel@vger.kernel.org,
        pinskia@gmail.com
References: <152261521484.30503.16131389653845029164.stgit@warthog.procyon.org.uk>
 <3465e0c6-f5b2-4c42-95eb-29361481f805@zytor.com>
In-Reply-To: <3465e0c6-f5b2-4c42-95eb-29361481f805@zytor.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

One thing I forgot to mention that would be quite useful is careful use 
of namespaces. For example, putting init functions in their own 
namespace would have not only make it a lot harder to call init 
functions from non-init functions by mistake (calling init::func() 
explicitly is a highly visible "I really do mean to do this."

However, it also let us do separate init versions of functions like 
cpu_feature_enable() that contain optimizations that aren't actually 
usable at init time (alternatives have not been applied.) The idea is 
*not* to change the code, but rather the compiler will simply prefer 
init:: functions from inside other init:: functions (a direct 
consequence of how namespaces work.)

	-hpa