Received: by 2002:a05:6602:2086:0:0:0:0 with SMTP id a6csp4466076ioa; Wed, 27 Apr 2022 04:36:56 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwgdtSv52ujtcYudOXvdMw0az8RYPVmawesFPIQ7OxImWKmfBXM3dZdpmLwUPJdwjUTICUW X-Received: by 2002:a17:90a:ee84:b0:1d9:27f3:eeeb with SMTP id i4-20020a17090aee8400b001d927f3eeebmr25841317pjz.66.1651059416447; Wed, 27 Apr 2022 04:36:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1651059416; cv=none; d=google.com; s=arc-20160816; b=ZwYl5YTGIBtBYxy8JC0+Uk2b5G5vjUP7p0/0gHVU/jtcDLtLDnwVDhb3bxbeK660/j BMIIh1OulkmGM6moMod/bq2Xq5hRGJrDyn/Sw89FweOkhNNqSILcSJ0J8b+BRnBFhP0x S0cTUvNFpkvOT2a0E80hSLQRBtc/lbKIyDge00K5MDKeXL5uJdnqyUx5izSkUeHr8nqH iYFc1IMlvgczPA8KpbxL3aGA6xXfzcCFZ66marSoEpYVelJ+J3AV7hpOJ5pT37V2R325 /cHxe3uTwCa4Edj/posnbvOuYNKXns/Mz+J1XKevlzCwG5WGdbIPhqwYNloHx8fbhnYX 7I3Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=MIMmsRd4TGXHkHuqVNiknPxYxan/XZ16Gjm6dh++myA=; b=0HPE7yCziQPafjOR0VgM6EO+IO9Kg+4siFQN3RyJudn0E7y79CnRl2yt81RsW8R0cZ LYsMzZU6IZpa3YwTyZSXUieDi5pHpEc2Ga9i0Qz/kOm4dQ83mZQtpkjrfiWX01S1hmLt AuCzWAsJldVjBL5mAm79AcrdB2iMRlNTYFDEqEmCUKpEcphTsKHbD/TySzjqUvLyXD3T SWZbNHwwQFWcpryeViNrVX8YUG8YWg8iuiz5GhgVVfnDOoYyWwY+50aSpy3i5jY8FHnf dXWGTaDxeisL5jUtbOtlFwjlskP3JRd6A8HtPxEuItlZhIcMC6T1gqMkbqEB2pfd5iWo xYGw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ecnrmmJj; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [23.128.96.19]) by mx.google.com with ESMTPS id y2-20020a17090322c200b0015164c6214bsi1566827plg.2.2022.04.27.04.36.56 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 27 Apr 2022 04:36:56 -0700 (PDT) Received-SPF: softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19; Authentication-Results: mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ecnrmmJj; spf=softfail (google.com: domain of transitioning linux-kernel-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 626BF49F4ED; Wed, 27 Apr 2022 03:27:06 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231348AbiD0JYu (ORCPT + 99 others); Wed, 27 Apr 2022 05:24:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33592 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229757AbiD0JYt (ORCPT ); Wed, 27 Apr 2022 05:24:49 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5A1AD28F963 for ; Wed, 27 Apr 2022 02:20:51 -0700 (PDT) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 2E08E61CEC for ; Wed, 27 Apr 2022 09:20:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 664F2C385AA; Wed, 27 Apr 2022 09:20:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1651051235; bh=m9uxew7Ob+mN18WzmXF2f6e5Z5voUIFfMjJGwq2tpr0=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=ecnrmmJjKkvpYal7Ghn5bftg1xtu7Z0Gme56Wvq6DjVirZBbOhPRm0lt2jBIuv9xu 0ONfHQ/Gey4P+DI8K4cAR/b0dWSQKRuIta1DfsqsJBRVGHVJprNh2XD7r7x5M0uU+E 3kEoSbKrCNRTIi3v5SyHv5br8RfVjDoi81AzfJu4= Date: Wed, 27 Apr 2022 11:20:31 +0200 From: Greg KH To: Lukasz Luba Cc: linux-kernel@vger.kernel.org, sudeep.holla@arm.com, dietmar.eggemann@arm.com, vincent.guittot@linaro.org, rafael@kernel.org, rostedt@goodmis.org, mingo@redhat.com Subject: Re: [PATCH v4] arch_topology: Trace the update thermal pressure Message-ID: References: <20220427080806.1906-1-lukasz.luba@arm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220427080806.1906-1-lukasz.luba@arm.com> X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Apr 27, 2022 at 09:08:06AM +0100, Lukasz Luba wrote: > Add trace event to capture the moment of the call for updating the thermal > pressure value. It's helpful to investigate how often those events occur > in a system dealing with throttling. This trace event is needed since the > old 'cdev_update' might not be used by some drivers. > > The old 'cdev_update' trace event only provides a cooling state > value: [0, n]. That state value then needs additional tools to translate > it: state -> freq -> capacity -> thermal pressure. This new trace event > just stores proper thermal pressure value in the trace buffer, no need > for additional logic. This is helpful for cooperation when someone can > simply sends to the list the trace buffer output from the platform (no > need from additional information from other subsystems). > > There are also platforms which due to some design reasons don't use > cooling devices and thus don't trigger old 'cdev_update' trace event. > They are also important and measuring latency for the thermal signal > raising/decaying characteristics is in scope. This new trace event > would cover them as well. > > We already have a trace point 'pelt_thermal_tp' which after a change to > trace event can be paired with this new 'thermal_pressure_update' and > derive more insight what is going on in the system under thermal pressure > (and why). > > Signed-off-by: Lukasz Luba Much better, thanks. I'll wait for Sudeep's comments/review before taking it into my tree. greg k-h