From: Andrew Morton <akpm@linux-foundation.org>
To: John Villalovos <sodarock@gmail.com>
Cc: Robert Richter <robert.richter@amd.com>,
Andi Kleen <andi@firstfloor.org>,
oprofile-list@lists.sf.net, linux-kernel@vger.kernel.org,
rostedt@goodmis.org, stable@kernel.org
Subject: Re: [PATCH] oprofile: remove double ring buffering
Date: Thu, 22 Apr 2010 16:04:11 -0700 [thread overview]
Message-ID: <20100422160411.cfcae4e1.akpm@linux-foundation.org> (raw)
In-Reply-To: <m2h5e61b72f1004220733n65451418p7c321f07eb5d6b58@mail.gmail.com>
On Thu, 22 Apr 2010 10:33:56 -0400
John Villalovos <sodarock@gmail.com> wrote:
> On Thu, Apr 1, 2010 at 3:02 PM, Robert Richter <robert.richter@amd.com> wrote:
> > On 01.04.10 03:17:25, Andi Kleen wrote:
> >> Got confirmation now this patch fixes most of the dropped oprofile
> >> samples problem on a particular intensive test on a large system.
> >> So now submitting the previous RFC formally.
> >> .34 / Stable candidate.
> >
> > Thanks Andi, will take a look at this next week.
>
> I was wondering what the state of this patch is. I don't see it in
> linux-2.6 or linux-next. or in
> git://git.kernel.org/pub/scm/linux/kernel/git/rric/oprofile.git
>
I queued it in my for-2.6.34-via-subsystem-maintainer pile. I'll start
sending those things out for everyone to ignore early next week I guess.
next prev parent reply other threads:[~2010-04-22 23:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-01 1:17 Andi Kleen
2010-04-01 15:49 ` [stable] " Greg KH
2010-04-01 19:02 ` Robert Richter
2010-04-01 19:11 ` Steven Rostedt
2010-04-04 10:01 ` Andi Kleen
2010-04-04 13:07 ` Steven Rostedt
2010-04-22 14:33 ` John Villalovos
2010-04-22 23:04 ` Andrew Morton [this message]
2010-04-23 9:00 ` Robert Richter
2010-04-23 15:38 ` Robert Richter
2010-04-23 15:38 ` Robert Richter
-- strict thread matches above, loose matches on Subject: below --
2010-03-20 0:03 Andi Kleen
2010-03-20 4:45 ` Steven Rostedt
2010-03-20 4:59 ` 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=20100422160411.cfcae4e1.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=andi@firstfloor.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sf.net \
--cc=robert.richter@amd.com \
--cc=rostedt@goodmis.org \
--cc=sodarock@gmail.com \
--cc=stable@kernel.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
Powered by JetHome