Received: by 2002:ac0:aed5:0:0:0:0:0 with SMTP id t21csp648472imb; Fri, 1 Mar 2019 10:08:31 -0800 (PST) X-Google-Smtp-Source: APXvYqz2grkjPMTzV5tBTdN8Y5U+AjCXHEpwHi2VjsSNdqr37BwOPdB5GI+fvEIaQ4TwU8khfDdV X-Received: by 2002:a63:4924:: with SMTP id w36mr5899992pga.227.1551463711135; Fri, 01 Mar 2019 10:08:31 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1551463711; cv=none; d=google.com; s=arc-20160816; b=aBqVDapQEx89mvD2tf+lXj/pq+0nOUEcWLCY5Uhv/+PMHUVs6c7fSgWN0bVmTU34WU s5r0I3F9CqXfzS8T2AkTjkF0OuJnSnKQsF6ToJtSm+IyZzkQsOB2Pb32YL75EP2sywOs aF25gt+WYoljSMKUnwPrwH7KFpiRH75bVCHn4n2zjRVgZiWJ2uQjAEEj6ue9Y3mZEiyR NBqA1DYyJMKnVcWDRJsjtedz3XpSlYtyqoQCwvtagjZjEyA27FejH53PUz1K9Hxj4Wpc xHssVybKATnFJPNAOeXiZT6/dxI1mNWjb/kmB3KwHf98hD/mpJMKwFBBh/gX+Z+xrmHM wCmA== 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:mime-version :references:in-reply-to:date:cc:to:from:subject:message-id; bh=c5xuTVB4DBfwPsaY5eKXtJFQ3gBeLtKooBLrs2QC8wU=; b=yVHGE2Gat8J4qRpuuxq0S6JCxzXdthmqrNY35fY0qaEtHl6U9MbAhIKr503pQ+riGC 9ni6vPVmF4vmOSfxzo9OCDLTlhlY8Y/BH0VKL1mc4KOxInPX5kuODmSEK/mJEtoMgmeq EDuUtovYyDePx3whxhJ74A02auoiGAN8aoGjQGFXeMT0kxOuVO74psxytns/w8TwHpQr LEV81/F3RNpcm4faXvZ35GbrR6xipE9cYc9XvI8o92VZkE7udTGg+b8IRr3LW3FqcNrf cwd9Eag2UshrTPrvoYEQloyCUUHl/V4Y2zgZ8fvwH2ozkaRf4hKOLs38hcExuiMzVRMx uYfQ== 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 r10si20690885pgr.489.2019.03.01.10.08.16; Fri, 01 Mar 2019 10:08:31 -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 S2389514AbfCARj3 (ORCPT + 99 others); Fri, 1 Mar 2019 12:39:29 -0500 Received: from mga04.intel.com ([192.55.52.120]:23660 "EHLO mga04.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728331AbfCARj3 (ORCPT ); Fri, 1 Mar 2019 12:39:29 -0500 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 01 Mar 2019 09:39:28 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.58,428,1544515200"; d="scan'208";a="303633003" Received: from spandruv-mobl3.jf.intel.com ([10.252.135.12]) by orsmga005.jf.intel.com with ESMTP; 01 Mar 2019 09:39:27 -0800 Message-ID: Subject: Re: [RFT][PATCH 0/2] cpufreq: intel_pstate: Handle _PPC updates on global turbo disable/enable From: Srinivas Pandruvada To: "Rafael J. Wysocki" , Linux PM Cc: LKML , Viresh Kumar , Chen Yu , Gabriele Mazzotta Date: Fri, 01 Mar 2019 09:39:27 -0800 In-Reply-To: <9956076.F4luUDm1Dq@aspire.rjw.lan> References: <9956076.F4luUDm1Dq@aspire.rjw.lan> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.28.5 (3.28.5-1.fc28) Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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? 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 >