Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp1079540imb; Sat, 2 Mar 2019 02:22:20 -0800 (PST) X-Google-Smtp-Source: APXvYqzyrEQo6mqAqVLxcSYR2A/PMg/Jm5hJrNfoSoTBbj6U9Al0iQvDLIyK3VznZ61DBmHsaWlj X-Received: by 2002:a63:29c3:: with SMTP id p186mr9345710pgp.24.1551522140137; Sat, 02 Mar 2019 02:22:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551522140; cv=none; d=google.com; s=arc-20160816; b=oqdaT1mzzafSGIoB9keXqp0paY4qN03qSMTQSzHR2lmT8zu1VG1y+MarTdHs3rSh/r J7gfd8DI6eVEIinj+r80OG4JPXFcnQvBhYucQlG8ZTmrVAYLM/GHLmvyhogBGB08CFWI ORvEJH6lvby6i0MrtXgBW7qQE8ie+bfkPm1OTUXpJ0MGChY2JMLj2IZjpa0DmA2H7om5 6Gra4sAdPf6+tLoOEEmEHcwWVZ34VB4Dz1aKKDAO0nhjByHHSvh3Tsf0isuBm5wrYOxH 653BvrRFum83J2U2sp6fECmVkJCeXW4WNbilxNEjU8SKsPsqd4czCTQHagS744UMl9ZC fYtw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=h1X1WsSNIKefmvX5yJzaryJ4yxbBTg9F2SM5OP7b46Q=; b=SozXY1cbNU1YzAHu+Uq09o4554g9CWi3sSAiyGKSdlZjLvwuk9zdxelSNd4H45j1Sx PdWySGZEGq8ze9KUOKISUZXTncGsEOwEYdzcLkayHzNEsvcQEf2i8iAHveQB4vCtxsRl EVXZ4oaMgF59RWNlHqqMQYiT16bH/P4Namdjh9aEV+fHRjy/+SBpOHvkc6x3z++ZoOxC XPk6Susq8Ugwvrt3rih+B2NHLEZeVB3pLVfmV+pY0a8N3aKyAZZcQO2WE7uY06N/Za0y l9lXx4xI7Rnli9rLzYKaGISB/Hv086jgfhYpBY9njKa+sDvDlvwY5UOtZ6vBM/zCz6Ka 0UqQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q188si348488pfc.159.2019.03.02.02.21.51; Sat, 02 Mar 2019 02:22:20 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=intel.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726281AbfCBKVS (ORCPT + 99 others); Sat, 2 Mar 2019 05:21:18 -0500 Received: from mga01.intel.com ([192.55.52.88]:44994 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725986AbfCBKVS (ORCPT ); Sat, 2 Mar 2019 05:21:18 -0500 X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Mar 2019 02:21:17 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,431,1544515200"; d="scan'208";a="147944535" Received: from chenyu-office.sh.intel.com ([10.239.158.163]) by fmsmga002.fm.intel.com with ESMTP; 02 Mar 2019 02:21:16 -0800 Date: Sat, 2 Mar 2019 18:30:08 +0800 From: Yu Chen To: Srinivas Pandruvada Cc: "Rafael J. Wysocki" , Linux PM , LKML , Viresh Kumar , Gabriele Mazzotta Subject: Re: [RFT][PATCH 0/2] cpufreq: intel_pstate: Handle _PPC updates on global turbo disable/enable Message-ID: <20190302103008.GA7086@chenyu-office.sh.intel.com> References: <9956076.F4luUDm1Dq@aspire.rjw.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Mar 01, 2019 at 09:39:27AM -0800, Srinivas Pandruvada wrote: > On Fri, 2019-03-01 at 13:43 +0100, Rafael J. Wysocki wrote: > > Hi All, > > > > This is how I would fix the issue reported in BZ 200759 (see this > > patch series > > from Yu too: https://marc.info/?l=linux-pm&m=155137672924029&w=2). > > > > Patch [1/2] causes intel_pstate to update all policies if it gets a > > _PPC change > > notification and sees a global turbo disable/enable change. > > > > Patch [2/2] makes it update cpuinfo.max_freq for all policies in > > those cases. > > > > The patches here have not been tested yet, so testing would be much > > appreciated. > > > > Of course, comments are welcome too! > > This is the only platform, someone reported such issue. > Can we solve this by some udev rules and offline/online cpu 1-3 on > power source change? > Sound reasonable, we can deal with this BIOS problem in user space too. But if cpu0 could not be offline, how could cpu0's policy be updated? Thanks, Yu > There are examples of changing governors on power source change. > https://bbs.archlinux.org/viewtopic.php?id=207186 > > Here instead of changing governor just > echo 0 > /sys/devices/system/cpu/cpu1/online > echo 1 > /sys/devices/system/cpu/cpu1/online > echo 0 > > /sys/devices/system/cpu/cpu2/online > echo 1 > > /sys/devices/system/cpu/cpu2/online > echo 0 > > /sys/devices/system/cpu/cpu3/online > echo 1 > > /sys/devices/system/cpu/cpu3/online > > Thanks, > Srinivas > > > > > Thanks, > > Rafael > > >