Received: by 2002:ac0:a581:0:0:0:0:0 with SMTP id m1-v6csp1246191imm; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) X-Google-Smtp-Source: AAOMgpcoJm6YlsQCkb0Sri6kYTKLprUcFJyp6EhlnCkBbFIbn+THkhOOiNXSvc6u4x/75hIqfDrY X-Received: by 2002:a63:b047:: with SMTP id z7-v6mr13629107pgo.335.1530306986048; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1530306986; cv=none; d=google.com; s=arc-20160816; b=MyJRSWZNGkLFEGncrPq2jCASZFqYTaiDAL6k83Aj+2Qgm3ftlUAKCJQyf0I/zZmJDL a5RZWqQ0a9HZPE5aDysChJik7N9QxM7fe8OMBuOsxT+UrhBk4fG01HaNys517eOo3UFE nuy+ySs5glqPAwr2HHiVFc4J7VPrPfeQXHqtTHYWBRwfj/bmtszdA6J5LxWqFLA09bUs nNxesDSJTFp/BM1NS9sQV4Gez40/YcFE6g1eP9kDw4AdcN5Hb9YVpLgi15/ZC77uN6+s we7w0p6OL+s5w3STDIeHqDknfen/tg0mOk2XgdI57gPr2AXS4TPdklo+S68qkwBBGZwl C/Wg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:user-agent:references :message-id:in-reply-to:subject:cc:to:from:date :arc-authentication-results; bh=M1YtwxMdc2jPg888aUYpTXYI9n+XaU8fATxpMmtW5qg=; b=NhEaseHL8tw3P2OPT0ffwIwoytbWTHSMuLtR6FrqS9kOiaL/lB65gDwbZbepaiLWH2 Lz7OZRmMPKxgW7esmqHaiP9FxTlGmPvOMAoRvhsjKLADwhuodmwUwUSCF8fJfofm+v0r sPz+BLVa37NDTExtOjTbjxRe0Qzd9htmweAfG1Bdh91pS9FpzQvG8NCY7FsLdjVnB3lp 0Pi5QpofdT/EjWPdQADzOUGXzuwzITSmf3QqkCef5ghemMVukK89hEvQcp0/644Nz3XE LtK1OzNsnpcWPV4+UbCfmFJR+LQSVlpnCxXteYQ0HKFTBrB1li4IPfwWmCqDxVh0dHq4 7LXQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g2-v6si9644620pfi.212.2018.06.29.14.16.11; Fri, 29 Jun 2018 14:16:26 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755532AbeF2UJU (ORCPT + 99 others); Fri, 29 Jun 2018 16:09:20 -0400 Received: from Galois.linutronix.de ([146.0.238.70]:60499 "EHLO Galois.linutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753523AbeF2UJT (ORCPT ); Fri, 29 Jun 2018 16:09:19 -0400 Received: from p4fea482e.dip0.t-ipconnect.de ([79.234.72.46] helo=nanos) by Galois.linutronix.de with esmtpsa (TLS1.2:DHE_RSA_AES_256_CBC_SHA256:256) (Exim 4.80) (envelope-from ) id 1fYzhU-0006lK-6t; Fri, 29 Jun 2018 22:09:00 +0200 Date: Fri, 29 Jun 2018 22:08:59 +0200 (CEST) From: Thomas Gleixner To: Fenghua Yu cc: Dave Hansen , Ingo Molnar , H Peter Anvin , Ashok Raj , Alan Cox , Peter Zijlstra , Rafael Wysocki , Tony Luck , Ravi V Shankar , linux-kernel , x86 Subject: Re: [PATCH v2 2/4] x86/split_lock: Align x86_capability to unsigned long to avoid split locked access In-Reply-To: <20180629190346.GO18979@romley-ivt3.sc.intel.com> Message-ID: References: <1530282807-66555-1-git-send-email-fenghua.yu@intel.com> <1530282807-66555-3-git-send-email-fenghua.yu@intel.com> <20180629190346.GO18979@romley-ivt3.sc.intel.com> User-Agent: Alpine 2.21 (DEB 202 2017-01-01) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII X-Linutronix-Spam-Score: -1.0 X-Linutronix-Spam-Level: - X-Linutronix-Spam-Status: No , -1.0 points, 5.0 required, ALL_TRUSTED=-1,SHORTCIRCUIT=-0.0001 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 29 Jun 2018, Fenghua Yu wrote: > On Fri, Jun 29, 2018 at 06:35:39PM +0200, Thomas Gleixner wrote: > > On Fri, 29 Jun 2018, Dave Hansen wrote: > > > > Plus what enforces proper alignment for the other capability related > > u32 arrays? > > Do you want me to enforce unsigned long alignment for all that are used by > locked BTS/BTR? If there are variables which might be unaligned and accessed with locked instructions and you have them identified, then why are you asking whether they should be fixed? Ignoring them because they do not trigger #AC right now, is only the correct answer if you are a follower of the 'works by chance' cult. Yeah, I know that most of this industry just works by chance.... > Or you think we can push the patches upstream to allow broad test to find > and fix the issues? And all testers have access to the emulator running the design of the silicon with that new feature which will be released in a year from now? Aside of that we merge the patches when they are ready and done. And AFAICT there is enough homework to be finished before that. Thanks, tglx