From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-4.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E0D16C43441 for ; Thu, 15 Nov 2018 21:01:50 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id AE3482145D for ; Thu, 15 Nov 2018 21:01:50 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org AE3482145D Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=linux.intel.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2389077AbeKPHLO (ORCPT ); Fri, 16 Nov 2018 02:11:14 -0500 Received: from mga05.intel.com ([192.55.52.43]:44825 "EHLO mga05.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725846AbeKPHLO (ORCPT ); Fri, 16 Nov 2018 02:11:14 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga008.fm.intel.com ([10.253.24.58]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 15 Nov 2018 13:01:48 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,237,1539673200"; d="scan'208";a="86809005" Received: from linux.intel.com ([10.54.29.200]) by fmsmga008.fm.intel.com with ESMTP; 15 Nov 2018 13:01:48 -0800 Received: from [10.251.29.1] (kliang2-mobl1.ccr.corp.intel.com [10.251.29.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by linux.intel.com (Postfix) with ESMTPS id 5DC0A580475; Thu, 15 Nov 2018 13:01:47 -0800 (PST) Subject: Re: [PATCH 1/2] perf vendor events: Add stepping in CPUID string for x86 To: Jiri Olsa , acme@kernel.org Cc: mingo@redhat.com, peterz@infradead.org, linux-kernel@vger.kernel.org, namhyung@kernel.org, ak@linux.intel.com References: <20181114212416.15665-1-kan.liang@linux.intel.com> <20181115204411.GO9600@krava> From: "Liang, Kan" Message-ID: Date: Thu, 15 Nov 2018 16:01:46 -0500 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: <20181115204411.GO9600@krava> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 11/15/2018 3:44 PM, Jiri Olsa wrote: > On Wed, Nov 14, 2018 at 01:24:15PM -0800, kan.liang@linux.intel.com wrote: >> From: Kan Liang >> >> Perf tools cannot find the proper event list for Cascadelake server. >> Because Cascadelake server and Skylake server have the same CPU model >> number, which are used by perf tools to find the event list. >> >> The stepping for Skylake server is up to 4. >> The stepping for Cascadelake server starts from 5. >> The stepping can be used to distinguish between them. >> >> The stepping is added in get_cpuid_str(). >> The stepping information for Skylake server is updated in mapfile.csv. >> A x86 specific strcmp_cpuid_cmp() function is added to handle two CPUID >> formats in mapfile.csv, "vendor-family-model-stepping" and >> "vendor-family-model". >> - If a cpuid-regular-expression from the mapfile.csv using the new >> stepping format, a cpuid-string generated on the machine must include >> stepping. Otherwise, it is a mismatch. >> - If the cpuid-regular-expression using the old non-stepping format, >> the stepping in the cpuid-string will be ignored. >> >> The script, which using environment string "PERF_CPUID" without stepping >> on Skylake server, will be broken. If so, users must fix their scripts. >> >> Signed-off-by: Kan Liang > > Reviewed-by: Jiri Olsa > Thanks Jirka, Hi Arnaldo, Are you OK with the patch? If yes, I will go ahead to cleanup the *_cpuid_str() by moving them to header.c as promised. https://lkml.org/lkml/2018/11/15/929 The new patch will be on top of this patch. Thanks, Kan