Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Message-ID: <3a7c3a71-0be7-261e-20b7-54b4864eedb5@google.com>
Date:   Wed, 23 Mar 2022 16:48:57 -0700
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.0
Subject: Re: [RFC PATCH 10/47] mm: asi: Support for global non-sensitive
 direct map allocations
Content-Language: en-US
To:     Matthew Wilcox <willy@infradead.org>
Cc:     linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
        pbonzini@redhat.com, jmattson@google.com, pjt@google.com,
        oweisse@google.com, alexandre.chartre@oracle.com,
        rppt@linux.ibm.com, dave.hansen@linux.intel.com,
        peterz@infradead.org, tglx@linutronix.de, luto@kernel.org,
        linux-mm@kvack.org
References: <20220223052223.1202152-1-junaids@google.com>
 <20220223052223.1202152-11-junaids@google.com>
 <YjuL80tuvUbAWWKW@casper.infradead.org>
From:   Junaid Shahid <junaids@google.com>
In-Reply-To: <YjuL80tuvUbAWWKW@casper.infradead.org>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Precedence: bulk

Hi Matthew,

On 3/23/22 14:06, Matthew Wilcox wrote:
> On Tue, Feb 22, 2022 at 09:21:46PM -0800, Junaid Shahid wrote:
>> standard ASI instances. A new page flag is also added so that when
>> these pages are freed, they can also be unmapped from the ASI page
>> tables.
> 
> It's cute how you just throw this in as an aside.  Page flags are
> in high demand and just adding them is not to be done lightly.  Is
> there any other way of accomplishing what you want?
> 

I suppose we may be able to use page_ext instead. That certainly should be 
feasible for the PG_local_nonsensitive flag introduced in a later patch, 
although I am not completely sure about the PG_global_nonsensitive flag. That 
could get slightly tricky (though likely still possible to do) in case we need 
to allocate any non-sensitive memory before page_ext is initialized. One concern 
with using page_ext could be the extra memory usage on large machines.

BTW is page flag scarcity an issue on 64-bit systems as well, or only 32-bit 
systems? ASI is only supported on 64-bit systems (at least currently).

>> @@ -542,6 +545,12 @@ TESTCLEARFLAG(Young, young, PF_ANY)
>>   PAGEFLAG(Idle, idle, PF_ANY)
>>   #endif
>>   
>> +#ifdef CONFIG_ADDRESS_SPACE_ISOLATION
>> +__PAGEFLAG(GlobalNonSensitive, global_nonsensitive, PF_ANY);
> 
> Why is PF_ANY appropriate?
> 

I think we actually can use PF_HEAD here. That would make the alloc_pages path 
faster too. I'll change to that. (Initially I had gone with PF_ANY because in 
theory, you could allocate a compound page and then break it later and free the 
individual pages, but I don't know if that actually happens apart from THP, and 
certainly doesn't look like the case for any of the stuff that we have marked as 
non-sensitive.)

Thanks,
Junaid