public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@linux.intel.com>
To: 禹舟键 <ufo19890607@gmail.com>
Cc: peterz@infradead.org, mingo@redhat.com,
	alexander.shishkin@linux.intel.com, jolsa@kernel.org,
	David Ahern <dsahern@gmail.com>,
	namhyung@kernel.org, Wind Yu <yuzhoujian@didichuxing.com>,
	Milian Wolff <milian.wolff@kdab.com>,
	sj38.park@gmail.com, tardyp@gmail.com,
	linux-perf-users@vger.kernel.org, linux-kernel@vger.kernel.org,
	acme@redhat.com
Subject: Re: Port the period data column to centos6.7 for perf script
Date: Thu, 14 Sep 2017 21:21:54 -0700	[thread overview]
Message-ID: <20170915042154.GJ24844@tassilo.jf.intel.com> (raw)
In-Reply-To: <CAHCio2j0TO0dQtr1Dk+v0=k_1pzwzqhZCJBkUTHCKqFgNGdoBg@mail.gmail.com>

On Fri, Sep 15, 2017 at 10:24:15AM +0800, 禹舟键 wrote:
>    Hi, all.
>    I want to draw off-cpu flamegraph using perf script on centos6.7(kernel
>    version, 2.6.32-573), and I found perf script lacks the period data column
>    on that version. I  found two related patches, and modifed
>    builin-script.c in reference to those patches.
>    perf script:Add period data column authorJiri Olsa 2014-08-25 16:45:42
>    +0200 commit535aeaae7de821ba5d43ee2a204ee667ca95aae4
>    perf script: Add period as a default output column
>    commite8564b710c6df2c3aeb56c507c22f4bcfa4c0b2d)
> 

I would just compile the newer perf binary for Centos6 and use that. It should
work with older kernels too. That's much easier than backporting, and you get
many more features.

-Andi

       reply	other threads:[~2017-09-15  4:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAHCio2j0TO0dQtr1Dk+v0=k_1pzwzqhZCJBkUTHCKqFgNGdoBg@mail.gmail.com>
2017-09-15  4:21 ` Andi Kleen [this message]
2017-09-15 10:16   ` Port the period data column to centos6.7 for perf script Arnaldo Carvalho de Melo
2017-09-15  2:37 yuzhoujian

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=20170915042154.GJ24844@tassilo.jf.intel.com \
    --to=ak@linux.intel.com \
    --cc=acme@redhat.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=dsahern@gmail.com \
    --cc=jolsa@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=milian.wolff@kdab.com \
    --cc=mingo@redhat.com \
    --cc=namhyung@kernel.org \
    --cc=peterz@infradead.org \
    --cc=sj38.park@gmail.com \
    --cc=tardyp@gmail.com \
    --cc=ufo19890607@gmail.com \
    --cc=yuzhoujian@didichuxing.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