From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: "K. Prasad" <prasad@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, dipankar@in.ibm.com,
ego@in.ibm.com, mathieu.desnoyers@polymtl.ca, mingo@elte.hu
Subject: Re: [PATCH 0/2] Markers Implementation for RCU Tracing
Date: Thu, 29 Nov 2007 17:36:05 -0800 [thread overview]
Message-ID: <20071130013605.GK9059@linux.vnet.ibm.com> (raw)
In-Reply-To: <20071129184128.GA26466@in.ibm.com>
On Fri, Nov 30, 2007 at 12:11:28AM +0530, K. Prasad wrote:
> Hi,
> Please review the ensuing set of patches which convert the
> existing RCU tracing mechanism for Preempt RCU and RCU Boost into
> markers.
>
> These patches are based upon the 2.6.24-rc2-rt1 kernel tree.
>
> Along with marker transition, the RCU Tracing infrastructure has also
> been modularised to be built as a kernel module, thereby enabling
> runtime changes to the RCU Tracing infrastructure.
>
> Patch [1/2] - Patch that converts the Preempt RCU tracing in
> rcupreempt.c into markers.
>
> Patch [1/2] - Patch that converts the Preempt RCU Boost tracing in
> rcupreempt-boost.c into markers.
Looks good to me, though I do not pretend to understand the markers
implementation. I presume that the markers implementation forces the
varargs usage -- though the markers do seem quite a bit nicer in allowing
the formatting to be specified more naturally.
Thanx, Paul
next prev parent reply other threads:[~2007-11-30 1:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 18:41 [PATCH 0/2] Markers Implementation for RCU Tracing K. Prasad
2007-11-30 1:36 ` Paul E. McKenney [this message]
2007-11-30 9:07 ` K. Prasad
-- strict thread matches above, loose matches on Subject: below --
2007-11-29 19:31 K. Prasad
2007-12-31 6:00 K. Prasad
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=20071130013605.GK9059@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=dipankar@in.ibm.com \
--cc=ego@in.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mingo@elte.hu \
--cc=prasad@linux.vnet.ibm.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.