From: Frederic Weisbecker <fweisbec@gmail.com>
To: Peter Zijlstra <a.p.zijlstra@chello.nl>
Cc: LKML <linux-kernel@vger.kernel.org>, Ingo Molnar <mingo@elte.hu>,
Stephane Eranian <eranian@google.com>,
Borislav Petkov <bp@amd64.org>
Subject: Re: [RFC PATCH] perf: Split up buffer handling from core code
Date: Thu, 19 May 2011 03:07:46 +0200 [thread overview]
Message-ID: <20110519010744.GC1723@nowhere> (raw)
In-Reply-To: <1305767185-5771-1-git-send-email-fweisbec@gmail.com>
(Adding Borislav in Cc)
On Thu, May 19, 2011 at 03:06:25AM +0200, Frederic Weisbecker wrote:
> Keeping perf_output_copy() inlined is responsible
> of some ugliness there.
>
> A solution could be to have an internal only
> perf_output_copy_inline() version in internal.h
> and a wrapper in buffer.c that exports it.
>
> Or we can completely uninline it.
>
> Signed-off-by: Frederic Weisbecker <fweisbec@gmail.com>
> Cc: Ingo Molnar <mingo@elte.hu>
> Cc: Stephane Eranian <eranian@google.com>
> Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>
next prev parent reply other threads:[~2011-05-19 1:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-19 1:06 [RFC PATCH] perf: Split up buffer handling from core code Frederic Weisbecker
2011-05-19 1:07 ` Frederic Weisbecker [this message]
2011-05-19 7:31 ` Borislav Petkov
2011-05-19 8:32 ` Peter Zijlstra
2011-05-19 14:14 ` Frederic Weisbecker
2011-05-19 14:43 ` Peter Zijlstra
2011-05-19 14:59 ` Frederic Weisbecker
2011-05-19 15:14 ` Peter Zijlstra
2011-05-19 15:15 ` Frederic Weisbecker
2011-05-19 17:20 ` Ingo Molnar
2011-05-19 17:23 ` Frederic Weisbecker
2011-05-19 17:55 ` [PATCH] " Frederic Weisbecker
2011-05-31 18:22 ` Frederic Weisbecker
2011-06-01 7:06 ` Ingo Molnar
2011-06-09 11:43 ` [tip:perf/core] " tip-bot for Frederic Weisbecker
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=20110519010744.GC1723@nowhere \
--to=fweisbec@gmail.com \
--cc=a.p.zijlstra@chello.nl \
--cc=bp@amd64.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.