public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Borislav Petkov <bp@amd64.org>
Cc: Peter Zijlstra <peterz@infradead.org>,
	Ingo Molnar <mingo@elte.hu>, LKML <linux-kernel@vger.kernel.org>,
	Borislav Petkov <borislav.petkov@amd.com>,
	Stephane Eranian <eranian@google.com>
Subject: Re: [PATCH 1/2] perf: Carve out cgroup-related code
Date: Wed, 11 May 2011 15:33:43 +0200	[thread overview]
Message-ID: <20110511133340.GB1846@nowhere> (raw)
In-Reply-To: <1305119816-26280-2-git-send-email-bp@amd64.org>

(Adding Stephane in Cc)

On Wed, May 11, 2011 at 03:16:55PM +0200, Borislav Petkov wrote:
> From: Borislav Petkov <borislav.petkov@amd.com>
> 
> Move cgroup perf support into a different compilation module -
> kernel/events/cgroup.c - thus slimming perf_event.c some more.
> 
> While at it,
> 
> * push some oneliners into perf_event.h now that they're used in
> multiple .c files.
> 
> * drop is_cgroup_event() check for perf_cgroup_defer_enabled() at its
> callsite in __perf_event_enable since the latter does the check anyway.
> 
> No functional change.
> 
> Signed-off-by: Borislav Petkov <borislav.petkov@amd.com>

BTW, before you do it yourself, I have a patch pending that splits the buffer
part from the core.

Just to avoid effort duplicates... :)

  reply	other threads:[~2011-05-11 16:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 13:16 [PATCH 0/2] perf: Split it some more Borislav Petkov
2011-05-11 13:16 ` [PATCH 1/2] perf: Carve out cgroup-related code Borislav Petkov
2011-05-11 13:33   ` Frederic Weisbecker [this message]
2011-05-11 13:48     ` Borislav Petkov
2011-05-11 13:16 ` [PATCH 2/2] perf: Carve out callchain functionality Borislav Petkov
2011-05-11 13:30   ` Frederic Weisbecker
2011-05-11 13:49     ` Borislav Petkov

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=20110511133340.GB1846@nowhere \
    --to=fweisbec@gmail.com \
    --cc=borislav.petkov@amd.com \
    --cc=bp@amd64.org \
    --cc=eranian@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.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