All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Borislav Petkov <bp@amd64.org>
Cc: Peter Zijlstra <a.p.zijlstra@chello.nl>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	osrc-patches <osrc-patches@elbe.amd.com>
Subject: Re: [RFC PATCH] perf: Carve out cgroup-related code
Date: Thu, 12 May 2011 12:36:44 +0200	[thread overview]
Message-ID: <20110512103644.GH9937@elte.hu> (raw)
In-Reply-To: <20110511170912.GA27362@aftab>


* Borislav Petkov <bp@amd64.org> wrote:

> Done, patch below. I've moved all exports local to kernel/events/* to
> internal.h. Branch at
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/bp/bp.git perf-split

Beyond the things Peter noticed, there's also this new bit in perf_event.h:

enum event_type_t {
        EVENT_FLEXIBLE = 0x1,
        EVENT_PINNED = 0x2,
        EVENT_ALL = EVENT_FLEXIBLE | EVENT_PINNED,
};

this got there from core.c, albeit it's only core.c that uses it.

If then this should move to internal.h - or stay local to core.c.

Thanks,

	Ingo

  parent reply	other threads:[~2011-05-12 10:36 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-11 12:11 [RFC PATCH] perf: Carve out cgroup-related code Borislav Petkov
2011-05-11 13:46 ` Peter Zijlstra
2011-05-11 14:00   ` Ingo Molnar
2011-05-11 14:02   ` Borislav Petkov
2011-05-11 14:13     ` Ingo Molnar
2011-05-11 14:31       ` Borislav Petkov
2011-05-11 15:21         ` Ingo Molnar
2011-05-11 17:09           ` Borislav Petkov
2011-05-12  8:51             ` Peter Zijlstra
2011-05-12  8:54               ` Peter Zijlstra
2011-05-12 10:18               ` Borislav Petkov
2011-05-12 14:31                 ` Frederic Weisbecker
2011-05-12 15:13                   ` Lin Ming
2011-05-14  8:44                   ` Borislav Petkov
2011-05-14 13:02                     ` Frederic Weisbecker
2011-05-12 10:36             ` Ingo Molnar [this message]
2011-05-12 10:54               ` Borislav Petkov
2011-05-12 11:03                 ` 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=20110512103644.GH9937@elte.hu \
    --to=mingo@elte.hu \
    --cc=a.p.zijlstra@chello.nl \
    --cc=bp@amd64.org \
    --cc=fweisbec@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=osrc-patches@elbe.amd.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 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.