Received: by 2002:ac0:a679:0:0:0:0:0 with SMTP id p54csp466475imp; Wed, 20 Feb 2019 03:26:45 -0800 (PST) X-Google-Smtp-Source: AHgI3IaH5oEO5lcau+1wo6JjiqSF4MTizthoRa1r5ST5/s69vhVM+3SFybEMX6bIW/kCqk/yqNW7 X-Received: by 2002:a17:902:74cb:: with SMTP id f11mr34107919plt.180.1550662004936; Wed, 20 Feb 2019 03:26:44 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550662004; cv=none; d=google.com; s=arc-20160816; b=OFiyTkx6S4FTBB6wN9UhbwsDGtK5Bvt/uaXrP/IXJ+2bOvcYKqvXTtoGL70Fr521LH Pcx79OscQmIJ23asZJ0x1ckpIsamfEtLbx0ZdQNL/XDOKMU06UYVrz8YYtcLcSwBXDog PtqV3oazKZWP1oXqCunYmu4qMwf1udU8rQXVQ6HScBAc3Qy6TJusiee4VFI/R48LJz1R TT9bRWTn5uhIru2uibUosZCcvG/ytZtX4BrrX9N6DBh1uWQCy7Q3N/FKqy0MM+otar/l ajICGGLZldoWm+Kose/kP5zdg9TSRTec8tE+Tr5VgZRlL5tS8eowgYAzON6VX6CGGUst UIZA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=Pej40aTzZudntREJijTOj+YRqKj+1YHrS16H3FeI+r8=; b=aL+glV0SYpm52YKutbGpD4lWRsGLXHiBiDaRooTYrqeCLbcrCpvWnjIfS8bZlh0MLh 2WKWR6K7yKNBh+a9lEjPO/sOfdvbf7LKSb8rz+wt1eNp9BbLxF7mO7IqBtkcyHCzfuV2 aAJ/moWlp9hV3Y1HBzDxwHUXTTqL2R6MfJgmDEGTVI8PHoZoxOH/CJT27J9ZJctBuzu9 6nRG5GAOCtujl1OjV4Th1n7n62jta423yDZRlW6vcUdNHdXcPD8SFnk5Y3wpCwUUPUjL M961B2v9IlKkkUO7X6j3vAN2zQPJpU3s33frYJ125qGHt6imCsIMorBF/UnNrPD/urui Lsyg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=BJ0v47rp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id w15si5295196pgt.332.2019.02.20.03.26.29; Wed, 20 Feb 2019 03:26:44 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=BJ0v47rp; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726523AbfBTLYw (ORCPT + 99 others); Wed, 20 Feb 2019 06:24:52 -0500 Received: from mail-it1-f194.google.com ([209.85.166.194]:35567 "EHLO mail-it1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726197AbfBTLYw (ORCPT ); Wed, 20 Feb 2019 06:24:52 -0500 Received: by mail-it1-f194.google.com with SMTP id v72so14622645itc.0; Wed, 20 Feb 2019 03:24:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=Pej40aTzZudntREJijTOj+YRqKj+1YHrS16H3FeI+r8=; b=BJ0v47rpp3ckMeIuXkx5NOU1uoboEA17K9GolsCpwuiEAUzNsZ30UMQwLymaUmtqpx aTvntCNMuLPZp534rx+gVP894yvpq3XKBCpxT5EypAnI373n476zOdq8bU2gjihaNJzc f+UnGeQO0zvX4wrYjs+r81R16AxRSC8AFjHb67DPKZgEaNDvNn82ufEPoSomOvqlDkxH 4AzbL4mGBdrz8FPNNVM6AK4MfmezkKQD8v4Nm736TFk1tFwhwbx27Lcok8lVSFdv5uHx T+I15HeXvKshy0LuPhnHvkF0sffbDZl8M9BGzb9JNxPlulA5NSvdOK/SFhDlXBanNhKg Kekw== 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:content-transfer-encoding; bh=Pej40aTzZudntREJijTOj+YRqKj+1YHrS16H3FeI+r8=; b=SFBL99MkhhqtDkdF8vDvvsfWaZr6zKD6YGV7Sjk8AWEBXF5+T1DNtd3cW5Nn3Nal0j w98p0O3eOnRupZLOYSDcQ+OXWJa9ZHAHF1ZqT1XzLoCCjFGqbHMvP3gDKpPcLvF2rsNF ikXqyHRh+VsF69CaDkv8L4mKbX+tpPGDcWpjQZ2ytUUtAThAM80a4AZjOf4YenlW0OeI MjBOr3RHT7mrJDZbKddORxIb268Inlfpkj1ZqQWPkKzLH5SecDzKt1sJlMIS0KbUqjfe f4gi1hK953gtm+134RukapSly+iqPAaE8bnXRlxA3TADsKQBs00w2gI/FSoks9mE+5oG M/6A== X-Gm-Message-State: AHQUAuYPGHkS3RU8NJDX3w94C8wGVh+tgfioKMAdVzC7PGw61pGnVU56 5qgnSFHugLFwiZVOg7eXD5Em8YqthJxe7L3tg0Y= X-Received: by 2002:a24:ee8c:: with SMTP id b134mr5711190iti.162.1550661890717; Wed, 20 Feb 2019 03:24:50 -0800 (PST) MIME-Version: 1.0 References: <20190220101017.19587-1-e.velu@criteo.com> <1d9ff7a8-5f05-6554-d019-9665536aea84@criteo.com> In-Reply-To: From: Erwan Velu Date: Wed, 20 Feb 2019 12:24:38 +0100 Message-ID: Subject: Re: [PATCH] cpufreq: Report if CPU doesn't report boost technologies To: "Rafael J. Wysocki" Cc: Erwan Velu , "Rafael J. Wysocki" , Viresh Kumar , "open list:CPU FREQUENCY SCALING FRAMEWORK" , open list Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org I tried to put the message in a way to stay neutral, not saying if its a real error or not. Just reporting we were not able to find any boost cap on it. Erwan, Le mer. 20 f=C3=A9vr. 2019 =C3=A0 12:16, Rafael J. Wysocki a =C3=A9crit : > > On Wed, Feb 20, 2019 at 11:52 AM Erwan Velu wrote: > > > > > > Le 20/02/2019 =C3=A0 11:41, Rafael J. Wysocki a =C3=A9crit : > > > On Wed, Feb 20, 2019 at 11:11 AM Erwan Velu = wrote: > > >> There is some rare cases where CPB (and possibly IDA) are missing on= processors. > > >> This is the case fixed by commit f7f3dc00f612 ("x86/cpu/AMD: Fix err= atum 1076 (CPB bit)") and following. > > >> > > >> In such context, the boost status isn't reported by /sys/devices/sys= tem/cpu/cpufreq/boost. > > > So I'm not really sure why the extra message is needed. It looks lik= e > > > this message will always be printed (with debug output enabled) if th= e > > > current cpufreq driver is acpi-cpufreq and the boost attribute is not > > > present in sysfs, which only is the case if CPB/IDA aren't there. > > > > > > Does it provide any additional information, then? > > > > When you know and read the code, yes this patch is too obvious. > > > > As a user when I was troubleshooting why the boost entry was _not_ > > populated on one CPU and was populated on another. > > > > Running acpi-cpufreq with dyndbg, I would have found useful to get that > > hint. > > > > So that could helps users that never read that part of the code and > > which are tricked into that configuration. > > OK, I see your point. > > I'll queue up the patch, but I guess I'll change the message.