From: Andi Kleen <ak@linux.intel.com>
To: Ravi Bangoria <ravi.bangoria@linux.ibm.com>
Cc: acme@kernel.org, haiyanx.song@intel.com,
alexander.shishkin@linux.intel.com, jolsa@redhat.com,
namhyung@kernel.org, kan.liang@linux.intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] perf/x86/pmu-events: Fix Kernel_Utilization metric
Date: Fri, 6 Dec 2019 08:29:40 -0800 [thread overview]
Message-ID: <20191206162940.GC752382@tassilo.jf.intel.com> (raw)
In-Reply-To: <20191204162121.29998-1-ravi.bangoria@linux.ibm.com>
On Wed, Dec 04, 2019 at 09:51:21PM +0530, Ravi Bangoria wrote:
> Kernel Utilization should divide ref cycles spent in kernel with total
> ref cycles.
Reviewed-by: Andi Kleen <ak@linux.intel.com>
-Andi
next prev parent reply other threads:[~2019-12-06 16:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-04 16:21 [PATCH] perf/x86/pmu-events: Fix Kernel_Utilization metric Ravi Bangoria
2019-12-06 16:29 ` Andi Kleen [this message]
2019-12-11 13:35 ` Arnaldo Carvalho de Melo
2019-12-17 11:31 ` [tip: perf/urgent] " tip-bot2 for Ravi Bangoria
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=20191206162940.GC752382@tassilo.jf.intel.com \
--to=ak@linux.intel.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=haiyanx.song@intel.com \
--cc=jolsa@redhat.com \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=namhyung@kernel.org \
--cc=ravi.bangoria@linux.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.