From: Chris Wright <chrisw@sous-sol.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: "Chris Wright" <chrisw@sous-sol.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Jeremy Fitzhardinge" <jeremy@goop.org>,
"Frédéric Weisbecker" <fweisbec@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Glauber de Oliveira Costa" <gcosta@redhat.com>,
"Rusty Russell" <rusty@rustcorp.com.au>,
"Pekka Enberg" <penberg@cs.helsinki.fi>
Subject: Re: [PATCH 0/2] [GIT PULL] tracing: various bug fixes
Date: Fri, 24 Apr 2009 08:12:01 -0700 [thread overview]
Message-ID: <20090424151201.GX3036@sequoia.sous-sol.org> (raw)
In-Reply-To: <20090424083648.GK24912@elte.hu>
* Ingo Molnar (mingo@elte.hu) wrote:
> * Chris Wright <chrisw@sous-sol.org> wrote:
> > OK, saves a whopping 200 bytes on my .config too ;-)
> >
> > text data bss dec hex filename
> > 8041385 1816009 1822720 11680114 b23972 vmlinux.orig
> >
> > text data bss dec hex filename
> > 8041181 1816009 1822720 11679910 b238a6 vmlinux
>
> This really demonstrates the cost of paravirt :-/
>
> Please lets not forget this patch - it makes sense regardless of
> whether it works around the bug i reported.
Yup, Steve picked it up and it's in his most recent ftrace pull request
to you.
thanks,
-chris
next prev parent reply other threads:[~2009-04-24 15:14 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 22:22 Steven Rostedt
2009-04-20 22:22 ` [PATCH 1/2] tracing: use recursive counter over irq level Steven Rostedt
2009-04-20 22:22 ` [PATCH 2/2] tracing: use nowakeup version of commit for function event trace tests Steven Rostedt
2009-04-20 22:41 ` Frederic Weisbecker
2009-04-20 22:57 ` Steven Rostedt
2009-04-21 8:23 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Ingo Molnar
2009-04-21 9:46 ` Ingo Molnar
2009-04-21 13:08 ` Steven Rostedt
2009-04-21 13:55 ` [PATCH][GIT PULL] ring-buffer: only warn on wrap if buffer is bigger than two pages Steven Rostedt
2009-04-21 14:35 ` Ingo Molnar
2009-04-21 14:54 ` Steven Rostedt
2009-04-21 16:22 ` Steven Rostedt
2009-04-21 14:03 ` [tip:tracing/core] " tip-bot for Steven Rostedt
2009-04-22 6:48 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Steven Rostedt
2009-04-22 11:47 ` Frederic Weisbecker
2009-04-22 13:49 ` Steven Rostedt
2009-04-22 17:10 ` Frederic Weisbecker
2009-04-22 17:17 ` Jeremy Fitzhardinge
2009-04-22 17:22 ` Steven Rostedt
2009-04-22 21:32 ` Steven Rostedt
2009-04-23 8:28 ` Ingo Molnar
2009-04-23 3:35 ` Steven Rostedt
2009-04-23 8:20 ` Ingo Molnar
2009-04-23 13:53 ` Steven Rostedt
2009-04-23 14:39 ` Steven Rostedt
2009-04-23 15:08 ` Steven Rostedt
2009-04-23 15:11 ` Ingo Molnar
2009-04-23 16:49 ` Jeremy Fitzhardinge
2009-04-23 17:21 ` Chris Wright
2009-04-23 18:02 ` Chris Wright
2009-04-23 18:33 ` Steven Rostedt
2009-04-23 18:43 ` Chris Wright
2009-04-24 8:36 ` Ingo Molnar
2009-04-24 15:12 ` Chris Wright [this message]
2009-04-29 6:16 ` [tip:tracing/core] x86: use native register access for native tlb flushing tip-bot for Chris Wright
2009-04-23 17:52 ` [PATCH 0/2] [GIT PULL] tracing: various bug fixes Steven Rostedt
2009-04-24 8:34 ` Ingo Molnar
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=20090424151201.GX3036@sequoia.sous-sol.org \
--to=chrisw@sous-sol.org \
--cc=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=gcosta@redhat.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=penberg@cs.helsinki.fi \
--cc=rostedt@goodmis.org \
--cc=rusty@rustcorp.com.au \
/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
Powered by JetHome