From: Ingo Molnar <mingo@elte.hu>
To: Jiri Olsa <jolsa@redhat.com>
Cc: "Arnaldo Carvalho de Melo" <acme@redhat.com>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
"Peter Zijlstra" <a.p.zijlstra@chello.nl>,
masami.hiramatsu.pt@hitachi.com, hpa@zytor.com,
ananth@in.ibm.com, davem@davemloft.net,
linux-kernel@vger.kernel.org, tglx@linutronix.de,
eric.dumazet@gmail.com, 2nddept-manager@sdl.hitachi.co.jp
Subject: Re: [PATCH 1/2] x86: separating entry text section
Date: Tue, 8 Mar 2011 17:15:24 +0100 [thread overview]
Message-ID: <20110308161524.GE1751@elte.hu> (raw)
In-Reply-To: <20110307181039.GB15197@jolsa.redhat.com>
* Jiri Olsa <jolsa@redhat.com> wrote:
> On Mon, Mar 07, 2011 at 04:29:21PM +0100, Ingo Molnar wrote:
> >
> > * Jiri Olsa <jolsa@redhat.com> wrote:
> >
> > > hi,
> > > any feedback?
> >
> > Did you get my reply below?
> >
> > Thanks,
> >
> > Ingo
> >
>
> hi,
>
> strange, I believe I did reply on this.. got missed
> somehow or I'm missing simething :) reattached..
hm, the direct mail to me got lost, but i found your reply in the lkml folder.
That's how i missed your reply.
> I made another test with "reseting" the system state as suggested and only for
> cache-misses together with instructions and cycles events.
>
> I can see even bigger drop of icache load misses than before
> from 19359739 to 16448709 (about 15%).
>
> The instruction/cycles count is slightly bigger in the patched
> kernel run though..
Ok, elapsed time is more stable, it went from:
> 0.205402048 seconds time elapsed ( +- 0.299% )
> 0.206267711 seconds time elapsed ( +- 0.138% )
to:
> 0.206072845 seconds time elapsed ( +- 0.276% )
> 0.206747566 seconds time elapsed ( +- 0.137% )
which is 0.1% slower, within the noise of the measurement.
Will apply the patches, thanks Jiri!
Thanks,
Ingo
next prev parent reply other threads:[~2011-03-08 16:15 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-14 15:12 [RFC,PATCH] kprobes - optimized kprobes might crash before setting kernel stack Jiri Olsa
2011-02-15 9:41 ` Masami Hiramatsu
2011-02-15 12:30 ` Jiri Olsa
2011-02-15 15:55 ` Masami Hiramatsu
2011-02-15 16:54 ` Jiri Olsa
2011-02-15 17:05 ` [PATCH] kprobes - do not allow optimized kprobes in entry code Jiri Olsa
2011-02-16 3:36 ` Masami Hiramatsu
2011-02-17 15:11 ` Ingo Molnar
2011-02-17 15:20 ` Jiri Olsa
2011-02-18 16:26 ` Jiri Olsa
2011-02-19 14:14 ` Masami Hiramatsu
2011-02-20 12:59 ` Ingo Molnar
2011-02-21 11:54 ` Jiri Olsa
2011-02-21 14:25 ` [PATCH 0/2] x86: separating entry text section + kprobes fix Jiri Olsa
2011-02-21 14:25 ` [PATCH 1/2] x86: separating entry text section Jiri Olsa
2011-02-22 3:22 ` Masami Hiramatsu
2011-02-22 8:09 ` Ingo Molnar
2011-02-22 12:52 ` Jiri Olsa
2011-03-07 10:44 ` Jiri Olsa
2011-03-07 15:29 ` Ingo Molnar
2011-03-07 18:10 ` Jiri Olsa
2011-03-08 16:15 ` Ingo Molnar [this message]
2011-03-08 20:15 ` [tip:perf/core] x86: Separate out " tip-bot for Jiri Olsa
2011-02-21 14:25 ` [PATCH 2/2] kprobes: disabling optimized kprobes for " Jiri Olsa
2011-02-22 3:22 ` Masami Hiramatsu
2011-03-08 20:16 ` [tip:perf/core] kprobes: Disabling " tip-bot for Jiri Olsa
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=20110308161524.GE1751@elte.hu \
--to=mingo@elte.hu \
--cc=2nddept-manager@sdl.hitachi.co.jp \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@redhat.com \
--cc=ananth@in.ibm.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fweisbec@gmail.com \
--cc=hpa@zytor.com \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu.pt@hitachi.com \
--cc=tglx@linutronix.de \
/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
all inboxes | Powered by JetHome®