Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752456AbbG1P2o (ORCPT ); Tue, 28 Jul 2015 11:28:44 -0400 Received: from mx1.redhat.com ([209.132.183.28]:60280 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752206AbbG1P2l (ORCPT ); Tue, 28 Jul 2015 11:28:41 -0400 Date: Tue, 28 Jul 2015 10:28:39 -0500 From: Josh Poimboeuf To: Andy Lutomirski Cc: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Michal Marek , Peter Zijlstra , Andy Lutomirski , Borislav Petkov , Linus Torvalds , Andi Kleen , Pedro Alves , Namhyung Kim , Bernd Petrovitsch , X86 ML , live-patching@vger.kernel.org, "linux-kernel@vger.kernel.org" Subject: Re: [PATCH v8 09/21] x86/paravirt: Align paravirt thunk functions at 16-byte boundaries Message-ID: <20150728152839.GA6737@treble.redhat.com> References: <9bf0871b9910ec93b9c2876194fbb8b6b45ae48a.1438093915.git.jpoimboe@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23.1-rc1 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 982 Lines: 22 On Tue, Jul 28, 2015 at 08:23:04AM -0700, Andy Lutomirski wrote: > On Tue, Jul 28, 2015 at 7:47 AM, Josh Poimboeuf wrote: > > Paravirt thunk functions aren't aligned, which can impact performance > > and is inconsistent with gcc-generated functions. > > > > Align them at 16-byte boundaries to be consistent with gcc functions. > > IMO stackvalidate shouldn't warn about this. We've discussed dropping > the alignment requirement entirely, since it seems to have little > benefit on modern CPUs. Stackvalidate didn't actually find this alignment issue. I just noticed it when fixing the frame pointer issue. If alignment no longer helps with performance on modern CPUS, it's fine to drop this patch. -- Josh -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/