public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jiri Olsa <jolsa@redhat.com>
To: Namhyung Kim <namhyung@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Ingo Molnar <mingo@kernel.org>, Paul Mackerras <paulus@samba.org>,
	Namhyung Kim <namhyung.kim@lge.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/6] perf tools: Save column length in perf_hpp_fmt
Date: Thu, 24 Jul 2014 14:10:10 +0200	[thread overview]
Message-ID: <20140724121010.GA7652@krava.brq.redhat.com> (raw)
In-Reply-To: <1404883694-5342-4-git-send-email-namhyung@kernel.org>

On Wed, Jul 09, 2014 at 02:28:11PM +0900, Namhyung Kim wrote:
> Save column length in the hpp format and pass it to print functions.
> This is a preparation for users to control column width in the output.

SNIP

> +
> +void perf_hpp__reset_width(struct perf_hpp_fmt *fmt, struct hists *hists)
> +{
> +	int idx;
> +
> +	if (perf_hpp__is_sort_entry(fmt))
> +		return perf_hpp__reset_sort_width(fmt, hists);
> +
> +	for (idx = 0; idx < PERF_HPP__MAX_INDEX; idx++) {
> +		if (fmt == &perf_hpp__format[idx])
> +			break;
> +	}
> +
> +	if (idx == PERF_HPP__MAX_INDEX)
> +		return;
> +
> +	switch (idx) {
> +	case PERF_HPP__OVERHEAD:
> +	case PERF_HPP__OVERHEAD_SYS:
> +	case PERF_HPP__OVERHEAD_US:
> +	case PERF_HPP__OVERHEAD_ACC:
> +		fmt->len = 8;
> +		break;
> +
> +	case PERF_HPP__OVERHEAD_GUEST_SYS:
> +	case PERF_HPP__OVERHEAD_GUEST_US:
> +		fmt->len = 9;
> +		break;

just curious.. why is it 9 for guest %, while we use 8 for host?
I understand that was the current state

jirka

  reply	other threads:[~2014-07-24 12:10 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-09  5:28 [PATCHSET 0/6] perf tools: Honor column width setting Namhyung Kim
2014-07-09  5:28 ` [PATCH 1/6] perf tools: Left-align output contents Namhyung Kim
2014-07-09  5:28 ` [PATCH 2/6] perf tools: Make __hpp__fmt() receive an additional len argument Namhyung Kim
2014-07-09  5:28 ` [PATCH 3/6] perf tools: Save column length in perf_hpp_fmt Namhyung Kim
2014-07-24 12:10   ` Jiri Olsa [this message]
2014-07-24 15:46     ` Namhyung Kim
2014-07-24 15:58       ` Jiri Olsa
2014-07-09  5:28 ` [PATCH 4/6] perf report: Honor column width setting Namhyung Kim
2014-07-24 12:47   ` Jiri Olsa
2014-07-24 15:51     ` Namhyung Kim
2014-07-24 12:57   ` Jiri Olsa
2014-07-24 13:57     ` Arnaldo Carvalho de Melo
2014-07-24 14:49       ` Jiri Olsa
2014-07-24 15:41         ` Namhyung Kim
2014-07-24 15:58           ` Jiri Olsa
2014-07-24 19:14             ` Arnaldo Carvalho de Melo
2014-07-09  5:28 ` [PATCH 5/6] perf top: Add -w option for setting column width Namhyung Kim
2014-07-09  5:28 ` [PATCH 6/6] perf tools: Add name field into perf_hpp_fmt Namhyung Kim
2014-07-21  9:07 ` [PATCHSET 0/6] perf tools: Honor column width setting Jiri Olsa
2014-07-23  7:40   ` Namhyung Kim
2014-07-24 13:11     ` Jiri Olsa
2014-07-24 13:59 ` Arnaldo Carvalho de Melo
2014-07-24 15:42   ` Namhyung Kim

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=20140724121010.GA7652@krava.brq.redhat.com \
    --to=jolsa@redhat.com \
    --cc=a.p.zijlstra@chello.nl \
    --cc=acme@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=namhyung.kim@lge.com \
    --cc=namhyung@kernel.org \
    --cc=paulus@samba.org \
    /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