Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1983695pxb; Thu, 4 Nov 2021 11:55:25 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxV/hUUeXDxFY8mfk1umIJPFgHHShTx3ec7yC9OaisKUBtUewtUeUJ06lh8ioD1RkE6P8/9 X-Received: by 2002:aa7:dc13:: with SMTP id b19mr56679059edu.145.1636052125226; Thu, 04 Nov 2021 11:55:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1636052125; cv=none; d=google.com; s=arc-20160816; b=EJoXKjhsgKKdoC4ygwC33l5Gz/zuZqjaUM7qS5X2dVHycpCJGJkZlT/u1+G3ZEJ9fX OCyB59A8ibHNC3RhAGPW485WvncI/H19dLw0UH8GZIHLqEckNV+/VKL1WCQeWy8m31Y6 M9hTjkQmxlp7qm6ZGutfDkQER4QaiS6Hz/RuPbDXw5W6S0SxMyWyvldUEIk0kaPRO0lt 5eyLFlTSMBUYXEw8/CV8nCIqKN3ANlnekExDDIUqS1sB5UUQyKZfMO0u6LmW932HWYKP cMrCDVe8q+NHzM0AFNFEYzvfNMGTXQRwd6w1UygqludDND+eZVtBD2/VwHxqTc+Jo4SW PBNQ== 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; bh=Ev5HXKkqWVCDbj/tditW3QWt6RjaGkutj3mkV4sBiWw=; b=An/yG1yFiEZIXpB6mV7louCRTkfaddQtO1tJAX+KI4E29BpfFo5qmeR1VdYK5Nb2ij rPxC0QWomvLkr6KZEzvzxW5pFqOum/Y1JzTuRPDtn4z0Vbz2sZYrqsEskRsyQJrjiZKB NvB2Nc6AJFjq48VnDo1PHNVfhpFOknL4X79CfP+H9XRO9ZDqmVw+rB2oniuNeoBqSMG8 3ZbeARHV5IW2qwih1Ha+s1815/DVLzfHDVYau64hW4AErdwjcVeu0ieib/Sn9mwmtq2n IlVlcY5fzPioIJE1+w52XYsfJs69ry0+hA1GUNJaUDDCzbFQiqhYePPRcuCuxJV1NfJg 3fdQ== ARC-Authentication-Results: i=1; mx.google.com; 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=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id dp11si11840152ejc.3.2021.11.04.11.54.59; Thu, 04 Nov 2021 11:55:25 -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; 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=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232340AbhKDSxk (ORCPT + 99 others); Thu, 4 Nov 2021 14:53:40 -0400 Received: from mail-oi1-f179.google.com ([209.85.167.179]:41618 "EHLO mail-oi1-f179.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232295AbhKDSxf (ORCPT ); Thu, 4 Nov 2021 14:53:35 -0400 Received: by mail-oi1-f179.google.com with SMTP id l15so10756799oie.8; Thu, 04 Nov 2021 11:50:57 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Ev5HXKkqWVCDbj/tditW3QWt6RjaGkutj3mkV4sBiWw=; b=F1PHV0hL2onpc7rlK02nbBuOosMoA3VkYQZo+x1gufRfJOPGZeFJ4e3ogvgyY9C/dB 75F+j81EZ/z8x4BHJcdZtXYRfZ5EnnzdXXrrhQ0rAl6iykFlA/tCWGNuzic6m2EvlvSa DHDaHbza2CCND+SD2H6J8lp0mEnvOaaWB/yoTp5OjPq1NKRI0XKsN5TH++NR6h9Sel3f 6F7Xq3NX+X2P1M6p77c7jvTqSMsNi+dI7zaEMiJyBOwRUhkzDmKOleB66BPb9xAiJj02 ZCQq/0bwDZx3MVRR5mKXsT6EwyHkojabIt/xDVY5sj06KsDzCgfDvFPnDQ1cx/WrLGDO rukw== X-Gm-Message-State: AOAM530qe64OWJjN8rYX0V9cJ9usjRZRnQJEg0u5ZIrEE/2km7GK/ilY 1x+LULvAxhdavXtgswSOqsFXVDsdLA4wPs9AdklmGi/Y X-Received: by 2002:aca:5c5:: with SMTP id 188mr17833435oif.154.1636051856998; Thu, 04 Nov 2021 11:50:56 -0700 (PDT) MIME-Version: 1.0 References: <20211104102230.123679-1-srinivas.pandruvada@linux.intel.com> In-Reply-To: <20211104102230.123679-1-srinivas.pandruvada@linux.intel.com> From: "Rafael J. Wysocki" Date: Thu, 4 Nov 2021 19:50:46 +0100 Message-ID: Subject: Re: [PATCH] cpufreq: intel_pstate: Clear HWP Status during HWP Interrupt enable To: Srinivas Pandruvada Cc: "Rafael J. Wysocki" , Viresh Kumar , Linux PM , Linux Kernel Mailing List , Len Brown Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Nov 4, 2021 at 11:22 AM Srinivas Pandruvada wrote: > > It is possible that some performance excursions happened before OS boot > or enable HWP interrupts. So clear MSR_HWP_STATUS bits when we enable > HWP interrupt. In this way a next excursion will results in a HWP > interrupt. > > The status bits of MSR_HWP_STATUS must be cleared (0) by software so > that a new status condition change will cause the hardware to set the > bit again and issue the notification. > > Fixes: 57577c996d73 ("cpufreq: intel_pstate: Process HWP Guaranteed change notification") > Signed-off-by: Srinivas Pandruvada > --- > drivers/cpufreq/intel_pstate.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/cpufreq/intel_pstate.c b/drivers/cpufreq/intel_pstate.c > index 1e6898dc76b6..54cf21896889 100644 > --- a/drivers/cpufreq/intel_pstate.c > +++ b/drivers/cpufreq/intel_pstate.c > @@ -1645,6 +1645,7 @@ static void intel_pstate_enable_hwp_interrupt(struct cpudata *cpudata) > > /* wrmsrl_on_cpu has to be outside spinlock as this can result in IPC */ > wrmsrl_on_cpu(cpudata->cpu, MSR_HWP_INTERRUPT, 0x01); > + wrmsrl_on_cpu(cpudata->cpu, MSR_HWP_STATUS, 0); > } > } > > -- Applied as 5.16-rc material, thanks!