From: Darren Hart <dvhart@infradead.org>
To: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
Cc: platform-driver-x86@vger.kernel.org, rjw@rjwysocki.net,
linux-kernel@vger.kernel.org, srinidhi.kasagar@intel.com,
qipeng.zha@intel.com, rajeev.d.muralidhar@intel.com,
sukumar.ghorai@intel.com, ong.hock.yu@intel.com,
aubrey.li@intel.com, david.ginat@intel.com
Subject: Re: [PATCH v4 1/5] platform:x86: Add Intel Telemetry Core Driver
Date: Mon, 11 Jan 2016 10:22:34 -0800 [thread overview]
Message-ID: <20160111182234.GB10643@malice.jf.intel.com> (raw)
In-Reply-To: <1452157529-10627-1-git-send-email-souvik.k.chakravarty@intel.com>
On Thu, Jan 07, 2016 at 02:35:29PM +0530, Souvik Kumar Chakravarty wrote:
> Intel PM Telemetry is a software mechanism via which various SoC
> PM and performance related parameters like PM counters, firmware
> trace verbosity, the status of different devices inside the SoC, etc
> can be monitored and analyzed. The different samples that may be
> monitored can be configured at runtime via exported APIs.
>
> This patch adds the telemetry core driver that implements basic
> exported APIs.
>
> Signed-off-by: Souvik Kumar Chakravarty <souvik.k.chakravarty@intel.com>
> ---
> arch/x86/include/asm/intel_telemetry.h | 147 +++++++++
> drivers/platform/x86/intel_telemetry_core.c | 464 +++++++++++++++++++++++++++
> 2 files changed, 611 insertions(+)
> create mode 100644 arch/x86/include/asm/intel_telemetry.h
> create mode 100644 drivers/platform/x86/intel_telemetry_core.c
>
> diff --git a/arch/x86/include/asm/intel_telemetry.h b/arch/x86/include/asm/intel_telemetry.h
> new file mode 100644
> index 0000000..ed65fe7
> --- /dev/null
> +++ b/arch/x86/include/asm/intel_telemetry.h
This file doesn't exist yet, and the compile fails with just this patch applied.
Souvik, please test each patch individually. The idea is to add independent
functional blocks such that they are easier to understand and review, but they
must be complete and cannot break the build.
Typically this would be something more like:
1 core
2 platform
3 debugfs
The MAINTAINERS and Makefile should be changed within each patch for the files
they affect (checkpatch enforces MAINTAIENRS).
It still won't build after patch 2/5 when the Makefile target is introduced.
--
Darren Hart
Intel Open Source Technology Center
prev parent reply other threads:[~2016-01-11 18:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-07 9:05 Souvik Kumar Chakravarty
2016-01-11 18:22 ` Darren Hart [this message]
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=20160111182234.GB10643@malice.jf.intel.com \
--to=dvhart@infradead.org \
--cc=aubrey.li@intel.com \
--cc=david.ginat@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ong.hock.yu@intel.com \
--cc=platform-driver-x86@vger.kernel.org \
--cc=qipeng.zha@intel.com \
--cc=rajeev.d.muralidhar@intel.com \
--cc=rjw@rjwysocki.net \
--cc=souvik.k.chakravarty@intel.com \
--cc=srinidhi.kasagar@intel.com \
--cc=sukumar.ghorai@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
Powered by JetHome