From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1752146AbdBBQKB (ORCPT <rfc822;w@1wt.eu>);
        Thu, 2 Feb 2017 11:10:01 -0500
Received: from mail-wj0-f194.google.com ([209.85.210.194]:33557 "EHLO
        mail-wj0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1751634AbdBBQJc (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 2 Feb 2017 11:09:32 -0500
Date: Thu, 2 Feb 2017 17:09:16 +0100
From: Ingo Molnar <mingo@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: "Ghannam, Yazen" <Yazen.Ghannam@amd.com>, x86-ml <x86@kernel.org>,
        Yves Dionne <yves.dionne@gmail.com>,
        Brice Goglin <Brice.Goglin@inria.fr>,
        Peter Zijlstra <peterz@infradead.org>,
        lkml <linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH] x86/CPU/AMD: Bring back Compute Unit ID
Message-ID: <20170202160916.GA12498@gmail.com>
References: <20170201200237.36s2jwjgxi24we66@pd.tnic>
 <CY4PR12MB16402B523C336338BC3667B1F84D0@CY4PR12MB1640.namprd12.prod.outlook.com>
 <20170201214421.ppw2ww3faxxu2jrm@pd.tnic>
 <CY4PR12MB16408B436D47B59E86A20698F84D0@CY4PR12MB1640.namprd12.prod.outlook.com>
 <20170201222507.qvcn6dsxucn6fqcv@pd.tnic>
 <20170201224150.ohb7f7jvbttnikkz@pd.tnic>
 <20170202121054.im3c3iiqp26a2dyb@pd.tnic>
 <20170202154359.fevz4fmwc6t4ew75@pd.tnic>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20170202154359.fevz4fmwc6t4ew75@pd.tnic>
User-Agent: Mutt/1.5.24 (2015-08-30)
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org


* Borislav Petkov <bp@alien8.de> wrote:

> On Thu, Feb 02, 2017 at 01:10:54PM +0100, Borislav Petkov wrote:
> > Now on to run the same thing on a bigger bulldozer.
> 
> It looks differently on the bigger box:
> 
> before:
> 
>  Performance counter stats for 'make -s -j17 bzImage' (3 runs):
>      143.807894000 seconds time elapsed                                          ( +-  0.89% )
> 
>  Performance counter stats for 'make -s -j17 bzImage' (3 runs):
>      147.109189694 seconds time elapsed                                          ( +-  0.49% )

If there's any doubt about the validity of the measurement I'd suggest doing:

	perf stat -a --sync --repeat 3 ...

... so that there's no perf overhead and skew from the many processes of a kernel 
build workload, plus the --sync should reduce IO related noise.

Or:

	perf stat --null --sync --repeat 3 ...

... will only measure elapsed time, but will do that very precisely and with very 
little overhead.

Thanks,

	Ingo