From: Steven Rostedt <rostedt@goodmis.org>
To: Joel Fernandes <joelaf@google.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
LKML <linux-kernel@vger.kernel.org>,
kernel-team@android.com
Subject: Re: [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events
Date: Wed, 4 Oct 2017 13:03:51 -0400 [thread overview]
Message-ID: <20171004130351.7a24d0ba@gandalf.local.home> (raw)
In-Reply-To: <CAJWu+ormUaN-vBsXwshs7N=jnofqd-OGnEpE1_Zcc68dsot3Tg@mail.gmail.com>
On Wed, 4 Oct 2017 09:56:33 -0700
Joel Fernandes <joelaf@google.com> wrote:
> > I don't see the protection in the patches. I will definitely test that
> > before pushing it anywhere.
>
> The protection added by CONFIG_PROVE_LOCKING was already there before
> my patches. I just moved the code around in patch 1/2, nothing changed
> in that patch. I already tested the combination of PROVE_LOCKING
> enabled and disabled and several other combinations on your -next
> tree. It all compiled fine. Here is my test script FWIW:
> (By the way, do you mean that another tree/branch than your -next or
> Linus's master has protection removed? If so, could you let me know
> which tree/branch?)
Using Linus's master is usually fine, but if you want to see what I'm
working on, just look at the ftrace/core branch of my linux-trace.git
tree on kernel.org. Note, that branch often rebases. My for-next branch
does not.
Also note, I'm currently looking to pull in Tom Zanussi's hist patch
series, and then I'll get to yours afterward.
-- Steve
next prev parent reply other threads:[~2017-10-04 17:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-29 21:22 [PATCH v7 1/2] tracing: Prepare to add preempt and irq trace events Joel Fernandes
2017-09-29 21:22 ` [PATCH v7 2/2] tracing: Add support for preempt and irq enable/disable events Joel Fernandes
2017-10-04 16:01 ` Peter Zijlstra
2017-10-04 16:43 ` Joel Fernandes
2017-10-06 8:59 ` Joel Fernandes
2017-10-05 23:28 ` Joel Fernandes
2017-10-05 23:29 ` Joel Fernandes
2017-10-06 7:07 ` Peter Zijlstra
2017-10-06 7:28 ` Joel Fernandes
2017-10-06 13:38 ` Steven Rostedt
2017-10-06 17:27 ` Joel Fernandes
2017-10-04 16:04 ` Peter Zijlstra
2017-10-04 16:31 ` Joel Fernandes
2017-10-04 16:44 ` Steven Rostedt
2017-10-04 16:56 ` Joel Fernandes
2017-10-04 17:03 ` Steven Rostedt [this message]
2017-10-04 20:13 ` Joel Fernandes
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=20171004130351.7a24d0ba@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=joelaf@google.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®