Received: by 2002:a05:6a10:9848:0:0:0:0 with SMTP id x8csp1077749pxf; Thu, 8 Apr 2021 22:25:47 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxMzxmcy22ey3w9pRCEL0UAQdpPCM2DHfTuMeImxHteH/9Rk98HbIHHbkblKOmcBht7k9sE X-Received: by 2002:a17:906:3385:: with SMTP id v5mr14415699eja.539.1617945947675; Thu, 08 Apr 2021 22:25:47 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1617945947; cv=none; d=google.com; s=arc-20160816; b=blBc7Ns5wbpJBKVjIVbmUvo+/QHlJcVO3AcUlLJwkWIRrFp35SvJ2teonc9OmTof/h cWnokuc56M0UwhRDVayHIRKVvCIfq5WKILTErePpqFU7+5bRHiIipJw7OQyftISMYM4F Mg/JjMYRCIfxUp1b0CnKG4gjvOp45pPuR9CTAHb++0MMoXATjT/XdIZwnM8rmG2Fb/rr awBJ1vrroyORhyOuPo866tmObbs2uSZlbZ1MLmZfTkAkfeKGFsTAlv/ZfC6/qp2oBgfL v7cfgcVeVbX7gtRuMOwE0m7a+1WYdZBJWWvVHUx/fe4fBTTF0mnk4epIQZNQXrUj8oyX Hlow== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=iDvYE3lo6mdtPyL38hcLZsUZ7A2Go0Bp2cFLK0Yzql8=; b=imY+FLci31F6JJKZ/TmLur84H8RyHvA9H+XZtyR9mILImF13FdjL5T+YMiKkXvjHG+ qJZ5n3LQvRn7fx5PO4E804P6It79rA9gUk8XFdJVc3+D3WIm3Q9nHvAOKxnopJdxvD0B u2CGWEaW2I5uK2UAfRdL5zBHpH6gasa7Hdkh7KeX3ClyDb/MF0uU5ipdkE3bbSH6lmdB 36g5qLVgabdNklPffvDK8PvScc/IF6QQbWLBcLyubTVU/iSKqcs01tfCdjdXXdYqN/9p 6Vv7OVmHqN0EtqQXIXG+oaUywdgMvoLMYlrvgq9dH1IXswv+WNlSBOxIqdMklCaWu7Gz z/Ew== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@telus.net header.s=google header.b=dTP+Zg0X; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=telus.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id lv19si1337530ejb.553.2021.04.08.22.25.25; Thu, 08 Apr 2021 22:25:47 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@telus.net header.s=google header.b=dTP+Zg0X; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=telus.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230219AbhDIFYB (ORCPT + 99 others); Fri, 9 Apr 2021 01:24:01 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49596 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231503AbhDIFYA (ORCPT ); Fri, 9 Apr 2021 01:24:00 -0400 Received: from mail-il1-x129.google.com (mail-il1-x129.google.com [IPv6:2607:f8b0:4864:20::129]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7737AC061765 for ; Thu, 8 Apr 2021 22:23:47 -0700 (PDT) Received: by mail-il1-x129.google.com with SMTP id b17so3763995ilh.6 for ; Thu, 08 Apr 2021 22:23:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telus.net; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=iDvYE3lo6mdtPyL38hcLZsUZ7A2Go0Bp2cFLK0Yzql8=; b=dTP+Zg0XNWCGh0/GeznXbP4zFivhq7Gf7UKRwBny6Ks7gGOxEJUkjX/tAK1GHpF/lD BVJjrx35Dm4dp9fhkx6HX+2lviAu6doNehUEW5O979DMX+LYSk8z87+Y5uuAlWgfEHyX FxuThKDDRnfO2+kgZpC1HF+Qm52L8DCzqf+hxPGjGc6329itw4PCSYYvp7M3iA/sFQbo UvEJ5TxV9/+hAjN00n8LtzmGh6NWepMFCk+3VQ5cA0LVjM85fa5C00Jy9wLFEo75vIJU sFP/HxH9ninIjQM203jbk0HfjhfVHnwJcrOPQT5RRkLj+iVQpz1uaJ4AOa0ybUuGSp5R MyiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=iDvYE3lo6mdtPyL38hcLZsUZ7A2Go0Bp2cFLK0Yzql8=; b=dHev0ul2HM0Hqo7/HYatIsdokfpPyL26tV+nq0E0Ixjou64q122v+rC7wMEgcBB1Hp 7b6Y2rFprmuPrz0n7MreG4LoqhBdoTC2IwwHs1ffsF6r3qIMb5pwqCP/lNSvO0XCKW1O vFiiGf/4ycSPNPt3DponMbddQUTtWwWOWABoIa/sLMAMFJieUUgNk1GOa2xPODNaLkEh bOjxrMqnZCMzN7cjAvPbn9WuKurxmuSslWsGNCYQxn04UMaWr7qP6uGWFmPyNkMgrSYc azHPcB49k96mvIuf3AB+XPNeRgPGMul+t5D7jYeQmDiCSJx8+X9g6WBzeO5ePc1ASlFC 9cIQ== X-Gm-Message-State: AOAM533vjHFTmko4R2+0QIOLURDV5qjzkXnFrbksRQUOoEo8KWCu2mbg JJs+qpI6/a7jfXHF/X0lvQ02/+IOqKHIi4VO8/Uwgw== X-Received: by 2002:a05:6e02:1a81:: with SMTP id k1mr41418ilv.18.1617945826941; Thu, 08 Apr 2021 22:23:46 -0700 (PDT) MIME-Version: 1.0 References: <20210404083354.23060-1-psampat@linux.ibm.com> In-Reply-To: <20210404083354.23060-1-psampat@linux.ibm.com> From: Doug Smythies Date: Thu, 8 Apr 2021 22:23:38 -0700 Message-ID: Subject: Re: [RFC v3 0/2] CPU-Idle latency selftest framework To: Pratik Rajesh Sampat Cc: rjw@rjwysocki.net, Daniel Lezcano , shuah@kernel.org, ego@linux.vnet.ibm.com, svaidy@linux.ibm.com, Linux PM list , Linux Kernel Mailing List , linux-kselftest@vger.kernel.org, pratik.r.sampat@gmail.com Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Pratik, I tried V3 on a Intel i5-10600K processor with 6 cores and 12 CPUs. The core to cpu mappings are: core 0 has cpus 0 and 6 core 1 has cpus 1 and 7 core 2 has cpus 2 and 8 core 3 has cpus 3 and 9 core 4 has cpus 4 and 10 core 5 has cpus 5 and 11 By default, it will test CPUs 0,2,4,6,10 on cores 0,2,4,0,2,4. wouldn't it make more sense to test each core once? With the source CPU always 0, I think the results from the results from the destination CPUs 0 and 6, on core 0 bias the results, at least in the deeper idle states. They don't make much difference in the shallow states. Myself, I wouldn't include them in the results. Example, where I used the -v option for all CPUs: --IPI Latency Test--- --Baseline IPI Latency measurement: CPU Busy-- SRC_CPU DEST_CPU IPI_Latency(ns) 0 0 101 0 1 790 0 2 609 0 3 595 0 4 737 0 5 759 0 6 780 0 7 741 0 8 574 0 9 681 0 10 527 0 11 552 Baseline Avg IPI latency(ns): 620 <<<< suggest 656 here ---Enabling state: 0--- SRC_CPU DEST_CPU IPI_Latency(ns) 0 0 76 0 1 471 0 2 420 0 3 462 0 4 454 0 5 468 0 6 453 0 7 473 0 8 380 0 9 483 0 10 492 0 11 454 Expected IPI latency(ns): 0 Observed Avg IPI latency(ns) - State 0: 423 <<<<< suggest 456 here ---Enabling state: 1--- SRC_CPU DEST_CPU IPI_Latency(ns) 0 0 112 0 1 866 0 2 663 0 3 851 0 4 1090 0 5 1314 0 6 1941 0 7 1458 0 8 687 0 9 802 0 10 1041 0 11 1284 Expected IPI latency(ns): 1000 Observed Avg IPI latency(ns) - State 1: 1009 <<<< suggest 1006 here ---Enabling state: 2--- SRC_CPU DEST_CPU IPI_Latency(ns) 0 0 75 0 1 16362 0 2 16785 0 3 19650 0 4 17356 0 5 17606 0 6 2217 0 7 17958 0 8 17332 0 9 16615 0 10 17382 0 11 17423 Expected IPI latency(ns): 120000 Observed Avg IPI latency(ns) - State 2: 14730 <<<< suggest 17447 here ---Enabling state: 3--- SRC_CPU DEST_CPU IPI_Latency(ns) 0 0 103 0 1 17416 0 2 17961 0 3 16651 0 4 17867 0 5 17726 0 6 2178 0 7 16620 0 8 20951 0 9 16567 0 10 17131 0 11 17563 Expected IPI latency(ns): 1034000 Observed Avg IPI latency(ns) - State 3: 14894 <<<< suggest 17645 here Hope this helps. ... Doug