linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Frederic Weisbecker <fweisbec@gmail.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Frederic Weisbecker <fweisbec@gmail.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Paul Mackerras <paulus@samba.org>,
	Arnaldo Carvalho de Melo <acme@infradead.org>
Subject: [GIT PULL] perf event scheduling updates
Date: Sat, 16 Jan 2010 14:40:05 +0100	[thread overview]
Message-ID: <1263649209-4343-1-git-send-regression-fweisbec@gmail.com> (raw)

Ingo,

Please pull the perf/scheduling branch that can be found at:

git://git.kernel.org/pub/scm/linux/kernel/git/frederic/random-tracing.git
	perf/scheduling

Thanks,
	Frederic
---

Frederic Weisbecker (4):
      perf/core: Split context's event group list into pinned and non-pinned lists
      list: Introduce list_rotate_left()
      perf: Round robin flexible groups of events using list_rotate_left()
      perf: Export software-only event group characteristic as a flag


 include/linux/list.h       |   14 +++
 include/linux/perf_event.h |    8 +-
 kernel/perf_event.c        |  262 +++++++++++++++++++++++++++-----------------
 3 files changed, 181 insertions(+), 103 deletions(-)

             reply	other threads:[~2010-01-16 13:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-16 13:40 Frederic Weisbecker [this message]
2010-01-16 13:40 ` [PATCH 1/4] perf/core: Split context's event group list into pinned and non-pinned lists Frederic Weisbecker
2010-01-16 13:40 ` [PATCH 2/4] list: Introduce list_rotate_left() Frederic Weisbecker
2010-01-16 13:40 ` [PATCH 3/4] perf: Round robin flexible groups of events using list_rotate_left() Frederic Weisbecker
2010-01-16 13:40 ` [PATCH 4/4] perf: Export software-only event group characteristic as a flag Frederic Weisbecker
2010-01-17  6:50 ` [GIT PULL] perf event scheduling updates 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=1263649209-4343-1-git-send-regression-fweisbec@gmail.com \
    --to=fweisbec@gmail.com \
    --cc=acme@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=paulus@samba.org \
    --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;
as well as URLs for NNTP newsgroup(s).