From: Robert Richter <robert.richter@amd.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: LKML <linux-kernel@vger.kernel.org>,
oprofile-list <oprofile-list@lists.sourceforge.net>
Subject: [GIT PULL] oprofile: updates for v2.6.34
Date: Wed, 4 Aug 2010 12:47:38 +0200 [thread overview]
Message-ID: <20100804104738.GJ26154@erda.amd.com> (raw)
Ingo,
please pull oprofile updates for v2.6.36:
git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git core
It's just a small number of patches, see the log below. The branch is
already in linux-next for a long time.
Thanks,
-Robert
$ git log --stat --first-parent cc49b092d308f8ea8634134b0d95d831a88a674b..729419f0090601406abe714c5f8872a3bd53ff68 | cat
commit 729419f0090601406abe714c5f8872a3bd53ff68
Author: Arnd Bergmann <arnd@arndb.de>
Date: Wed Jul 7 17:40:13 2010 -0400
oprofile: make event buffer nonseekable
The event buffer cannot deal with seeks, so
we should forbid that outright.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Cc: Robert Richter <robert.richter@amd.com>
Cc: oprofile-list@lists.sf.net
Signed-off-by: Robert Richter <robert.richter@amd.com>
drivers/oprofile/event_buffer.c | 3 ++-
1 files changed, 2 insertions(+), 1 deletions(-)
commit b12eab1a796a306caef7046b21a76efa35f5f489
Author: Denis Kirjanov <dkirjanov@hera.kernel.org>
Date: Tue Jun 1 15:43:34 2010 -0400
powerpc/oprofile: fix potential buffer overrun in op_model_cell.c
Fix potential initial_lfsr buffer overrun.
Writing past the end of the buffer could happen when index == ENTRIES
Signed-off-by: Denis Kirjanov <dkirjanov@kernel.org>
Cc: stable@kernel.org
Signed-off-by: Robert Richter <robert.richter@amd.com>
arch/powerpc/oprofile/op_model_cell.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
commit d8a382d2662822248a97ce9d670b90e68aefbd3a
Merge: 45c34e0 c6df8d5
Author: Robert Richter <robert.richter@amd.com>
Date: Fri Jun 4 11:33:10 2010 +0200
Merge remote branch 'tip/perf/urgent' into oprofile/urgent
commit 45c34e05c4e3d36e7c44e790241ea11a1d90d54e
Author: John Villalovos <sodarock@gmail.com>
Date: Fri May 7 12:41:40 2010 -0400
Oprofile: Change CPUIDS from decimal to hex, and add some comments
Back when the patch was submitted for "Add Xeon 7500 series support to
oprofile", Robert Richter had asked for a followon patch that
converted all the CPU ID values to hex.
I have done that here for the "i386/core_i7" and "i386/atom" class
processors in the ppro_init() function and also added some comments on
where to find documentation on the Intel processors.
Signed-off-by: John L. Villalovos <john.l.villalovos@intel.com>
Signed-off-by: Robert Richter <robert.richter@amd.com>
arch/x86/oprofile/nmi_int.c | 16 ++++++++++++++--
1 files changed, 14 insertions(+), 2 deletions(-)
next reply other threads:[~2010-08-04 10:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-04 10:47 Robert Richter [this message]
2010-08-04 10:49 ` [GIT PULL] oprofile: updates for v2.6.36 Robert Richter
2010-08-04 14:25 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2010-03-02 16:44 [GIT PULL] oprofile: updates for v2.6.34 Robert Richter
2010-03-04 10:50 ` Ingo Molnar
2010-03-04 17:44 ` Robert Richter
2010-03-09 11:27 ` Robert Richter
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=20100804104738.GJ26154@erda.amd.com \
--to=robert.richter@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oprofile-list@lists.sourceforge.net \
/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