From: Ingo Molnar <mingo@kernel.org>
To: Andi Kleen <ak@linux.intel.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Stephane Eranian <eranian@google.com>,
linux-kernel@vger.kernel.org, mingo@elte.hu, acme@redhat.com,
jolsa@redhat.com, zheng.z.yan@intel.com
Subject: Re: [PATCH v1 1/2] perf,x86: add Intel RAPL PMU support
Date: Tue, 8 Oct 2013 09:36:47 +0200 [thread overview]
Message-ID: <20131008073647.GC4455@gmail.com> (raw)
In-Reply-To: <20131007192258.GC3363@tassilo.jf.intel.com>
* Andi Kleen <ak@linux.intel.com> wrote:
> On Mon, Oct 07, 2013 at 08:08:10PM +0200, Peter Zijlstra wrote:
> > On Mon, Oct 07, 2013 at 10:55:42AM -0700, Andi Kleen wrote:
> > > This would in principle allow making it a module later (if perf ever
> > > supports that)
> >
> > IIRC its a few EXPORTs away from being able to do that.
>
> Great. With ~700k text that would be a good thing.
Nonsense, the real overhead of core perf + PMU drivers on x86-64 is around
150k.
The 700k overhead you claimed is not reproducible, at all, and I tested it
with your own config:
https://lkml.org/lkml/2013/10/8/62
700k in perf is nonsensical - it's an obvious lie really, the code sizes
of the relevant perf .o objects are nowhere even _close_ to that amount:
hubble:~/tip> size $(find . -name '*perf*.o')
text data bss dec hex filename
887 0 32 919 397 ./arch/x86/kernel/cpu/perfctr-watchdog.o
2932 680 96 3708 e7c ./arch/x86/kernel/cpu/perf_event_amd_uncore.o
14117 6361 1 20479 4fff ./arch/x86/kernel/cpu/perf_event_intel.o
23787 19541 264 43592 aa48 ./arch/x86/kernel/cpu/perf_event_intel_uncore.o
4531 1572 0 6103 17d7 ./arch/x86/kernel/cpu/perf_event_p4.o
1728 1121 0 2849 b21 ./arch/x86/kernel/cpu/perf_event_knc.o
4591 811 32 5434 153a ./arch/x86/kernel/cpu/perf_event_amd_ibs.o
13394 6797 116 20307 4f53 ./arch/x86/kernel/cpu/perf_event.o
3156 1483 32 4671 123f ./arch/x86/kernel/cpu/perf_event_amd_iommu.o
5322 4396 0 9718 25f6 ./arch/x86/kernel/cpu/perf_event_intel_ds.o
11383 1 0 11384 2c78 ./arch/x86/kernel/cpu/perf_event_intel_lbr.o
3636 1125 0 4761 1299 ./arch/x86/kernel/cpu/perf_event_amd.o
1282 544 0 1826 722 ./arch/x86/kernel/cpu/perf_event_p6.o
278 1 0 279 117 ./arch/x86/kernel/perf_regs.o
4844 88 12 4944 1350 ./drivers/acpi/processor_perflib.o
77 96 0 173 ad ./drivers/cpufreq/cpufreq_performance.o
232 64 0 296 128 ./drivers/devfreq/governor_performance.o
1972 4 64 2040 7f8 ./kernel/trace/trace_event_perf.o
So stop making that ridiculous claim without posting exact .config's
publicly.
Thanks,
Ingo
next prev parent reply other threads:[~2013-10-08 7:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 16:09 [PATCH v1 0/2] perf,x86: add Intel RAPL PMU support Stephane Eranian
2013-10-07 16:09 ` [PATCH v1 1/2] " Stephane Eranian
2013-10-07 17:55 ` Andi Kleen
2013-10-07 18:08 ` Peter Zijlstra
2013-10-07 19:22 ` Andi Kleen
2013-10-07 20:33 ` Peter Zijlstra
2013-10-08 7:36 ` Ingo Molnar [this message]
2013-10-07 20:58 ` Stephane Eranian
2013-10-07 21:45 ` Andi Kleen
2013-10-07 22:38 ` Stephane Eranian
2013-10-08 15:10 ` Stephane Eranian
2013-10-07 16:09 ` [PATCH v1 2/2] perf,x86: add RAPL hrtimer support Stephane Eranian
2013-10-07 16:19 ` [PATCH v1 0/2] perf,x86: add Intel RAPL PMU support Borislav Petkov
2013-10-07 16:24 ` Stephane Eranian
2013-10-07 16:42 ` Borislav Petkov
2013-10-07 16:29 ` Peter Zijlstra
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=20131008073647.GC4455@gmail.com \
--to=mingo@kernel.org \
--cc=acme@redhat.com \
--cc=ak@linux.intel.com \
--cc=eranian@google.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=zheng.z.yan@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;
as well as URLs for NNTP newsgroup(s).