public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: David Ahern <dsahern@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>,
	Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH] tools/perf: remove non-existent entries in MANIFEST
Date: Thu, 26 Sep 2013 13:11:27 -0300	[thread overview]
Message-ID: <20130926161127.GF26159@ghostprotocols.net> (raw)
In-Reply-To: <CALkWK0k=c9ov-FWaR8ocD-XjUOEQWCLhv-4OjWFkJYmfMRV=QQ@mail.gmail.com>

Em Thu, Sep 26, 2013 at 09:18:48PM +0530, Ramkumar Ramachandra escreveu:
> David Ahern wrote:
> > Did you create a tarfile after this change, unpack it somewhere out of three
> > and then verify perf builds?
> 
> Yeah, it builds fine. In fact, the archive generated from the current
> upstream is broken.

Could you please describe how it is broken?

[acme@zoo linux]$ git branch | grep '*'
* perf/urgent
[acme@zoo linux]$ git describe
v3.12-rc1-51-gc1bf214
[acme@zoo linux]$ make perf-tar-src-pkg
  TAR
[acme@zoo linux]$ mv perf-3.12.0-rc1.tar /tmp
[acme@zoo linux]$ cd /tmp
[acme@zoo tmp]$ tar xf perf-3.12.0-rc1.tar 
[acme@zoo tmp]$ cd perf-3.12.0-rc1
[acme@zoo perf-3.12.0-rc1]$ make -j4 -C tools/perf
    CHK -fstack-protector-all
    CHK -Wstack-protector
    CHK -Wvolatile-register-var
<SNIP>
    CC util/parse-events-flex.o
    AR libperf.a
    LINK perf
make: Leaving directory `/tmp/perf-3.12.0-rc1/tools/perf'
[acme@zoo perf-3.12.0-rc1]$
[acme@zoo perf-3.12.0-rc1]$ file tools/perf/perf
tools/perf/perf: ELF 64-bit LSB executable, x86-64, version 1 (SYSV),
dynamically linked (uses shared libs), for GNU/Linux 2.6.32,
BuildID[sha1]=0x4ccfe4a3c71572532c54a478fec49ad1b38f1f3a, not stripped
[acme@zoo perf-3.12.0-rc1]$ 
[acme@zoo perf-3.12.0-rc1]$ tools/perf/perf --help | head -6

 usage: perf [--version] [--help] COMMAND [ARGS]

 The most commonly used perf commands are:
   annotate        Read perf.data (created by perf record) and display
annotated code
   archive         Create archive with object files with build-ids found
in perf.data file
[acme@zoo perf-3.12.0-rc1]$ tools/perf/perf stat usleep 1

 Performance counter stats for 'usleep 1':

          1.034116 task-clock                #    0.495 CPUs utilized          
                 2 context-switches          #    0.002 M/sec                  
                 1 cpu-migrations            #    0.967 K/sec                  
               140 page-faults               #    0.135 M/sec                  
         1,024,416 cycles                    #    0.991 GHz                    
           730,998 stalled-cycles-frontend   #   71.36% frontend cycles
idle   
   <not supported> stalled-cycles-backend  
           553,592 instructions              #    0.54  insns per cycle        
                                             #    1.32  stalled cycles
                                             #    per insn
           105,979 branches                  #  102.483 M/sec                  
             8,030 branch-misses             #    7.58% of all branches        

       0.002088462 seconds time elapsed

[acme@zoo perf-3.12.0-rc1]$

- Arnaldo

  reply	other threads:[~2013-09-26 16:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-26 14:21 [PATCH] tools/perf: remove non-existent entries in MANIFEST Ramkumar Ramachandra
2013-09-26 15:14 ` David Ahern
2013-09-26 15:48   ` Ramkumar Ramachandra
2013-09-26 16:11     ` Arnaldo Carvalho de Melo [this message]
2013-09-27  2:02       ` Ramkumar Ramachandra

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=20130926161127.GF26159@ghostprotocols.net \
    --to=acme@ghostprotocols.net \
    --cc=a.p.zijlstra@chello.nl \
    --cc=artagnon@gmail.com \
    --cc=dsahern@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --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