From: "Bhardwaj, Rajneesh" <rajneesh.bhardwaj@linux.intel.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
Darren Hart <dvhart@infradead.org>,
Andy Shevchenko <andy@infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Rajneesh Bhardwaj <rajneesh.bhardwaj@intel.com>,
Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>,
matt.turner@intel.com, "Brown, Len" <len.brown@intel.com>,
Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@intel.com>
Subject: Re: [PATCH 4/4] platform/x86: intel_telemetry: report debugfs failure
Date: Wed, 26 Sep 2018 19:54:13 +0530 [thread overview]
Message-ID: <69ad420e-362c-d8c9-331f-056cdaefb1eb@linux.intel.com> (raw)
In-Reply-To: <CAHp75VcE+BY=8aKEGqzkDBVazLGtwNNCa1CYCKGirS1vBLVXPg@mail.gmail.com>
On 26-Sep-18 7:26 PM, Andy Shevchenko wrote:
> On Mon, Sep 3, 2018 at 9:05 PM Rajneesh Bhardwaj
> <rajneesh.bhardwaj@linux.intel.com> wrote:
>> On some Goldmont based systems such as ASRock J3455M the BIOS may not
>> enable the IPC1 device that provides access to the PMC and PUNIT. In
>> such scenarios, the ioss and pss resources from the platform device can
> IOSS
> PSS
Fine.
>
>> not be obtained and result in a invalid telemetry_plt_config.
> What is telemetry_plt_config?
Internal data structure that holds platform config, maintained by the
telemetry platform driver.
>
>> This is also applicable to the platforms where the BIOS supports IPC1
>> device under debug configurations but IPC1 is disabled by user or the
>> policy.
>>
>> This change allows user to know the reason for not seeing entries under
>> /sys/kernel/debug/telemetry/* when there is no apparent failure at boot.
>>
>> Cc: Matt Turner <matt.turner@intel.com>
>> Cc: Len Brown <len.brown@intel.com>
>> Cc: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
>> Cc: Kuppuswamy Sathyanarayanan <sathyanarayanan.kuppuswamy@intel.com>
>>
>> Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=198779
>>
> There should be not a blank line.
OK.
>
>> Acked-by: Matt Turner <matt.turner@intel.com>
>> Signed-off-by: Rajneesh Bhardwaj <rajneesh.bhardwaj@linux.intel.com>
>> +exit:
>> + pr_debug(pr_fmt(DRIVER_NAME) " Failed\n");
> Completely useless.
>
> Device core does it in generic way.
If i remove this print then perhaps there is no need of this patch.
Reason to print this is that the platform driver / core driver does not
show any error. In-fact they are even loaded in module table. OTOH, this
debugfs interface fails. This is very confusing to the users if they
check the lsmod output so i feel this print might help.
>
next prev parent reply other threads:[~2018-09-26 14:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-03 18:04 [PATCH 1/4] platform/x86: intel_pmc_core: Show Latency Tolerance info Rajneesh Bhardwaj
2018-09-03 18:04 ` [PATCH 2/4] platform/x86: intel_pmc_core: Fix LTR IGNORE Max offset Rajneesh Bhardwaj
2018-09-26 13:57 ` Andy Shevchenko
2018-09-26 14:24 ` Bhardwaj, Rajneesh
2018-09-03 18:04 ` [PATCH 3/4] platform/x86: intel_pmc_core: Decode Snoop / Non Snoop LTR Rajneesh Bhardwaj
2018-09-26 13:53 ` Andy Shevchenko
2018-09-26 14:19 ` Bhardwaj, Rajneesh
2018-09-26 17:42 ` Andy Shevchenko
2018-09-03 18:04 ` [PATCH 4/4] platform/x86: intel_telemetry: report debugfs failure Rajneesh Bhardwaj
2018-09-26 13:56 ` Andy Shevchenko
2018-09-26 14:24 ` Bhardwaj, Rajneesh [this message]
2018-09-26 17:18 ` Andy Shevchenko
[not found] ` <bb2d01ce-e2c9-18a8-7409-8c014989f732@linux.intel.com>
2018-09-28 9:10 ` Rajneesh Bhardwaj
2018-09-26 13:48 ` [PATCH 1/4] platform/x86: intel_pmc_core: Show Latency Tolerance info Andy Shevchenko
2018-09-26 14:11 ` Bhardwaj, Rajneesh
2018-09-26 17:14 ` Andy Shevchenko
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=69ad420e-362c-d8c9-331f-056cdaefb1eb@linux.intel.com \
--to=rajneesh.bhardwaj@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=andy@infradead.org \
--cc=dvhart@infradead.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.turner@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=rajneesh.bhardwaj@intel.com \
--cc=sathyanarayanan.kuppuswamy@intel.com \
--cc=souvik.k.chakravarty@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;
as well as URLs for NNTP newsgroup(s).