From: Robert Richter <robert.richter@amd.com>
To: oprofile-list <oprofile-list@lists.sourceforge.net>
Cc: Ingo Molnar <mingo@elte.hu>, Paul Mackerras <paulus@samba.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Oprofile kernel git tree
Date: Mon, 13 Oct 2008 22:20:23 +0200 [thread overview]
Message-ID: <20081013202022.GE23557@erda.amd.com> (raw)
The OProfile git tree is now up-to-date:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git
Currently there are these branches:
Test branches (non fast-forward):
master all patches
next patches for next kernel
Feature branches (patches not yet ready for upstream, fast-forward only):
arch-perfmon
multiplexing
Upstream branches (patches for the architcture maintainers and
linux-next, fast-forward only):
x86-oprofile-for-tip
oprofile-for-tip
powerpc-for-paul
Please use the master/next branches as the latest OProfile kernel for
testing.
Pending patches are:
powerpc-for-paul:
Carl Love (1):
powerpc/cell/oprofile: fix mutex locking for spu-oprofile
Roel Kluin (1):
powerpc/cell/oprofile: vma_map: fix test on overlay_tbl_offset
x86-oprofile-for-tip:
Andi Kleen (4):
oprofile: drop const in num counters field
oprofile: Don't report Nehalem as core_2
oprofile: Implement Intel architectural perfmon support
oprofile: discover counters for op ppro too
Thanks,
-Robert
--
Advanced Micro Devices, Inc.
Operating System Research Center
email: robert.richter@amd.com
next reply other threads:[~2008-10-13 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 20:20 Robert Richter [this message]
2008-10-13 20:33 ` Oprofile kernel git tree Andi Kleen
2008-10-14 13:56 ` Robert Richter
2008-10-14 14:10 ` Andi Kleen
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=20081013202022.GE23557@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
--cc=paulus@samba.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