From: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
To: platform-driver-x86@vger.kernel.org
Cc: dvhart@infradead.org, andy@infradead.org,
linux-kernel@vger.kernel.org, rajneesh.bhardwaj@intel.com,
Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
Subject: [PATCH v1 2/5] platform/x86: intel_telemetry: Fix suspend stats
Date: Thu, 16 Nov 2017 15:48:14 +0530 [thread overview]
Message-ID: <1510827497-25188-3-git-send-email-souvik.k.chakravarty@intel.com> (raw)
In-Reply-To: <1510827497-25188-1-git-send-email-souvik.k.chakravarty@intel.com>
Suspend stats are not reported consistently due to a limitation in the PMC
firmware. This limitation causes a delay in updating the s0ix counters and
residencies in the telemetry log upon s0ix exit. As a consequence, reading
these counters from the suspend-exit notifier may result in zero read.
This patch fixes this issue by cross-verifying the s0ix residencies from
the GCR TELEM registers in case the counters are not incremented in the
telemetry log after suspend.
This fixes https://bugzilla.kernel.org/show_bug.cgi?id=197833
Reported-and-tested-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>
Signed-off-by: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
---
drivers/platform/x86/intel_telemetry_debugfs.c | 39 ++++++++++++++++++++++++++
1 file changed, 39 insertions(+)
diff --git a/drivers/platform/x86/intel_telemetry_debugfs.c b/drivers/platform/x86/intel_telemetry_debugfs.c
index 4249e826..d0fce8c 100644
--- a/drivers/platform/x86/intel_telemetry_debugfs.c
+++ b/drivers/platform/x86/intel_telemetry_debugfs.c
@@ -74,6 +74,8 @@
#define TELEM_IOSS_DX_D0IX_EVTS 25
#define TELEM_IOSS_PG_EVTS 30
+#define TELEM_LO_HI_TO64(lo, hi) ((u64)(lo) + ((u64)(hi)<<32))
+
#define TELEM_DEBUGFS_CPU(model, data) \
{ X86_VENDOR_INTEL, 6, model, X86_FEATURE_ANY, (unsigned long)&data}
@@ -858,6 +860,7 @@ static int pm_suspend_exit_cb(void)
static u32 suspend_shlw_ctr_exit, suspend_deep_ctr_exit;
static u64 suspend_shlw_res_exit, suspend_deep_res_exit;
struct telemetry_debugfs_conf *conf = debugfs_conf;
+ u32 shlw_lo, shlw_hi, deep_lo, deep_hi;
int ret, index;
if (!suspend_prep_ok)
@@ -890,6 +893,42 @@ static int pm_suspend_exit_cb(void)
goto out;
}
+ /* Due to some design limitations in the firmware, sometimes the
+ * counters do not get updated by the time we reach here. As a
+ * workaround, we try to see if this was a genuine case of sleep
+ * failure or not by cross-checking from PMC GCR registers directly.
+ */
+ if ((suspend_shlw_ctr_exit == suspend_shlw_ctr_temp) &&
+ (suspend_deep_ctr_exit == suspend_deep_ctr_temp)) {
+ ret = intel_pmc_gcr_read(PMC_GCR_TELEM_SHLW_S0IX_LO_REG,
+ &shlw_lo);
+ if (ret < 0)
+ goto out;
+
+ ret = intel_pmc_gcr_read(PMC_GCR_TELEM_SHLW_S0IX_HI_REG,
+ &shlw_hi);
+ if (ret < 0)
+ goto out;
+
+ ret = intel_pmc_gcr_read(PMC_GCR_TELEM_DEEP_S0IX_LO_REG,
+ &deep_lo);
+ if (ret < 0)
+ goto out;
+
+ ret = intel_pmc_gcr_read(PMC_GCR_TELEM_DEEP_S0IX_HI_REG,
+ &deep_hi);
+ if (ret < 0)
+ goto out;
+
+ suspend_shlw_res_exit = TELEM_LO_HI_TO64(shlw_lo, shlw_hi);
+ if (suspend_shlw_res_exit > suspend_shlw_res_temp)
+ suspend_shlw_ctr_exit++;
+
+ suspend_deep_res_exit = TELEM_LO_HI_TO64(deep_lo, deep_hi);
+ if (suspend_deep_res_exit > suspend_deep_res_temp)
+ suspend_deep_ctr_exit++;
+ }
+
suspend_shlw_ctr_exit -= suspend_shlw_ctr_temp;
suspend_deep_ctr_exit -= suspend_deep_ctr_temp;
suspend_shlw_res_exit -= suspend_shlw_res_temp;
--
2.7.4
next prev parent reply other threads:[~2017-11-16 13:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 10:18 [PATCH v1 0/5] platform/x86: intel_telemetry: Fix counters and formatting Souvik Kumar Chakravarty
2017-11-16 10:18 ` [PATCH v1 1/5] platform/x86: intel_pmc_ipc: Fix register names Souvik Kumar Chakravarty
2017-11-17 12:49 ` Andy Shevchenko
2017-11-16 10:18 ` Souvik Kumar Chakravarty [this message]
2017-11-17 13:27 ` [PATCH v1 2/5] platform/x86: intel_telemetry: Fix suspend stats Andy Shevchenko
2017-11-16 10:18 ` [PATCH v1 3/5] platform/x86: intel_telemetry: Fix local variables Souvik Kumar Chakravarty
2017-11-17 13:29 ` Andy Shevchenko
2017-11-16 10:18 ` [PATCH v1 4/5] platform/x86: intel_telemetry: Remove redundancies Souvik Kumar Chakravarty
2017-11-17 13:33 ` Andy Shevchenko
2017-11-16 10:18 ` [PATCH v1 5/5] platform/x86: intel_telemetry: Improve S0ix logs Souvik Kumar Chakravarty
2017-11-17 13:36 ` Andy Shevchenko
2017-11-17 13:37 ` [PATCH v1 0/5] platform/x86: intel_telemetry: Fix counters and formatting Andy Shevchenko
2017-11-20 3:12 ` Chakravarty, Souvik K
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1510827497-25188-3-git-send-email-souvik.k.chakravarty@intel.com \
--to=souvik.k.chakravarty@intel.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®