From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932709AbdJaSZ7 (ORCPT ); Tue, 31 Oct 2017 14:25:59 -0400 Received: from mga14.intel.com ([192.55.52.115]:15520 "EHLO mga14.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932628AbdJaSZ5 (ORCPT ); Tue, 31 Oct 2017 14:25:57 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.44,325,1505804400"; d="scan'208";a="915936937" From: "Yu, Fenghua" To: Borislav Petkov , "Kammela, Gayatri" CC: "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+PjsggAAHDUA= Date: Tue, 31 Oct 2017 18:25:55 +0000 Message-ID: <3E5A0FA7E9CA944F9D5414FEC6C712207589C94F@ORSMSX106.amr.corp.intel.com> References: <1509412829-23380-1-git-send-email-gayatri.kammela@intel.com> <20171031100619.q5asiqkbuqi2cecp@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.138] 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 v9VIQ4of023367 > On Tuesday, October 31, 2017 11:03 AM, Yu, Fenghua wrote > > On Tuesday, October 31, 2017 3:06 AM, Borislav Petkov wrote: > > On Mon, Oct 30, 2017 at 06:20:29PM -0700, Gayatri Kammela wrote: > > > #define X86_FEATURE_AVX512VBMI (16*32+ 1) /* AVX512 Vector Bit > > Manipulation instructions*/ > > > > So we have previous AVX512 feature bits which do not separate AVX512 > > with a "_" but the new ones do. I think we should unify this and the > > SDM should be fixed too. > > This patch exactly follows the names in the spec. > > As you said, the legacy code doesn't follow spec naming strictly and the spec > doesn't have uniform naming convention either. We are contacting spec > author to see if we can follow the same naming convention in the future > specs. The spec author doesn't want to change the legacy names to insert "_" in order to have uniform names. The "_" in a name is just for readability. So in the future specs, there will be mixed names, some with "_" and some without "_". 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. Thanks. -Fenghua