From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sean Christopherson Subject: Re: [PATCH v5 5/5] x86/kvm: Avoid dynamic allocation of pvclock data when SEV is active Date: Thu, 6 Sep 2018 13:39:26 -0700 Message-ID: <20180906203926.GA5717@linux.intel.com> References: <1536234182-2809-1-git-send-email-brijesh.singh@amd.com> <1536234182-2809-6-git-send-email-brijesh.singh@amd.com> <20180906122423.GA11144@zn.tnic> <20180906135041.GB32336@linux.intel.com> <20180906141825.GB370@linux.intel.com> <20180906184750.GB4570@linux.intel.com> <20180906194710.GA16605@linux.intel.com> <9126c92f-ad3b-a5b6-ac44-416405489a7e@amd.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Borislav Petkov , x86@kernel.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, Tom Lendacky , Thomas Gleixner , "H. Peter Anvin" , Paolo Bonzini , Radim =?utf-8?B?S3LEjW3DocWZ?= To: Brijesh Singh Return-path: Content-Disposition: inline In-Reply-To: <9126c92f-ad3b-a5b6-ac44-416405489a7e@amd.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Thu, Sep 06, 2018 at 03:20:46PM -0500, Brijesh Singh wrote: > > > On 09/06/2018 02:47 PM, Sean Christopherson wrote: > ... > > >> > >>Yes, the auxiliary array will dumped into the regular .bss when > >>CONFIG_AMD_MEM_ENCRYPT=n. Typically it will be few k, I am not > >>sure if its worth complicating the code to save those extra memory. > >>Most of the distro's have CONFIG_AMD_MEM_ENCRYPT=y anyways. > > > >I just realized that we'll try to create a bogus array if 'NR_CPUS <= > >HVC_BOOT_ARRAY_SIZE'. A bit ugly, but we could #ifdef away both that > >and CONFIG_AMD_MEM_ENCRYPT=n in a single shot, e.g.: > > > >#if defined(CONFIG_AMD_MEM_ENCRYPT) && NR_CPUS > HVC_BOOT_ARRAY_SIZE > >#define HVC_AUX_ARRAY_SIZE \ > > PAGE_ALIGN((NR_CPUS - HVC_BOOT_ARRAY_SIZE) * \ > > sizeof(struct pvclock_vsyscall_time_info)) > >static struct pvclock_vsyscall_time_info > > hv_clock_aux[HVC_AUX_ARRAY_SIZE] __decrypted __aligned(PAGE_SIZE); > >#endif > > > > The HVC_BOOT_ARRAY_SIZE macro uses sizeof(..) and to my understanding > the sizeof operators are not allowed in '#if'. Anyway, I will try to see > if it can be used, if not then I will stick to CONFIG_AMD_MEM_ENCRYPT > check. Hmm, we'll need something otherwise 'NR_CPUS - HVC_BOOT_ARRAY_SIZE' will wrap and cause build errors.