lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Tue, 21 Aug 2018 17:19:38 +0200 From: Borislav Petkov <bp@...e.de> To: Brijesh Singh <brijesh.singh@....com> Cc: "x86@...nel.org" <x86@...nel.org>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Lendacky, Thomas" <Thomas.Lendacky@....com>, Thomas Gleixner <tglx@...utronix.de>, Paolo Bonzini <pbonzini@...hat.com>, Pavel Tatashin <pasha.tatashin@...cle.com> Subject: Re: SEV guest regression in 4.18 On Tue, Aug 21, 2018 at 09:37:56AM -0500, Brijesh Singh wrote: > Those variables are accessed immediately by the tsc calibration code > path hence we will not able to delay the allocation. If you mean, check_tsc_sync_source/_target(), those are called pretty late, AFAICT. And I see a setup_arch() -> init_mem_mapping -> ... -> kernel_physical_mapping_init() call which happens much earlier. Again, AFAICT. You probably should try it though, to make sure. -- Regards/Gruss, Boris. SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg) --
Powered by blists - more mailing lists