From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932742AbdJaThd (ORCPT ); Tue, 31 Oct 2017 15:37:33 -0400 Received: from mga05.intel.com ([192.55.52.43]:36533 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751366AbdJaThc (ORCPT ); Tue, 31 Oct 2017 15:37:32 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,325,1505804400"; d="scan'208";a="144397444" From: "Yu, Fenghua" To: Borislav Petkov CC: "Kammela, Gayatri" , "linux-kernel@vger.kernel.org" , "x86@kernel.org" , "hpa@linux.intel.com" , Thomas Gleixner , "Kleen, Andi" , "Shankar, Ravi V" , "Neri, Ricardo" , "Zhong, Yang" Subject: RE: [PATCH v2] x86/cpufeatures: Enable new SSE/AVX/AVX512 cpu features Thread-Topic: [PATCH v2] x86/cpufeatures: Enable new SSE/AVX/AVX512 cpu features Thread-Index: AQHTUjAA/9Nsz1zP/kWB1VQZPwjC1qL+PjsggAAHDUCAAHkKAP//m8Eg Date: Tue, 31 Oct 2017 19:37:29 +0000 Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712207589CA3A@ORSMSX106.amr.corp.intel.com> References: <1509412829-23380-1-git-send-email-gayatri.kammela@intel.com> <20171031100619.q5asiqkbuqi2cecp@pd.tnic> <3E5A0FA7E9CA944F9D5414FEC6C712207589C94F@ORSMSX106.amr.corp.intel.com> <20171031183258.uqqhe6qdyivx3t6f@pd.tnic> In-Reply-To: <20171031183258.uqqhe6qdyivx3t6f@pd.tnic> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-product: dlpe-windows dlp-version: 11.0.0.116 dlp-reaction: no-action x-originating-ip: [10.22.254.139] Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from base64 to 8bit by nfs id v9VJbcoq027705 > On Tuesday, October 31, 2017 11:33 AM, Borislav Petkov wrote: > On Tue, Oct 31, 2017 at 06:25:55PM +0000, Yu, Fenghua wrote: > > We may need to send a patch to fix a few legacy names that don't match > > exactly specs, e.g. AVX512VBMI as you mentioned. > > Or we can make them all uniform and ignore the spec. It's not like they would > be harder to grep afterwards. Should we change the legacy names as well? User apps may use the names already. Changing the names may break the apps. If we do make all uniform, do you prefer adding "_" after AVX512? Thanks. -Fenghua