From mboxrd@z Thu Jan 1 00:00:00 1970 From: Borislav Petkov Subject: Re: [PATCH 3/5] x86/kvm: Convert some slow-path static_cpu_has() callers to boot_cpu_has() Date: Sun, 31 Mar 2019 17:12:48 +0200 Message-ID: <20190331151248.GB15073@zn.tnic> References: <20190330112022.28888-1-bp@alien8.de> <20190330112022.28888-4-bp@alien8.de> <2f71cb35-46b2-9ed5-28b3-c6eb5e647b46@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Cc: LKML , Nadav Amit , Andy Lutomirski , Peter Zijlstra , "H. Peter Anvin" , Ingo Molnar , Joerg Roedel , kvm@vger.kernel.org, Radim =?utf-8?B?S3LEjW3DocWZ?= , Thomas Gleixner , x86@kernel.org To: Paolo Bonzini Return-path: Content-Disposition: inline In-Reply-To: <2f71cb35-46b2-9ed5-28b3-c6eb5e647b46@redhat.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: kvm.vger.kernel.org On Sun, Mar 31, 2019 at 04:20:11PM +0200, Paolo Bonzini wrote: > These are not slow path. Those functions do a *lot* of stuff like a bunch of MSR reads which are tens of cycles each at least. I don't think a RIP-relative MOV and a BT: movq boot_cpu_data+20(%rip), %rax # MEM[(const long unsigned int *)&boot_cpu_data + 20B], _45 btq $59, %rax #, _45 are at all noticeable. On latest AMD and Intel uarch those are 2-4 cycles, according to https://agner.org/optimize/instruction_tables.ods -- Regards/Gruss, Boris. Good mailing practices for 400: avoid top-posting and trim the reply.