lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1505846668.29775.13.camel@tzanussi-mobl.amr.corp.intel.com>
Date:   Tue, 19 Sep 2017 13:44:28 -0500
From:   Tom Zanussi <tom.zanussi@...ux.intel.com>
To:     Steven Rostedt <rostedt@...dmis.org>
Cc:     tglx@...utronix.de, mhiramat@...nel.org, namhyung@...nel.org,
        vedang.patel@...el.com, bigeasy@...utronix.de,
        joel.opensrc@...il.com, joelaf@...gle.com,
        mathieu.desnoyers@...icios.com, baohong.liu@...el.com,
        linux-kernel@...r.kernel.org, linux-rt-users@...r.kernel.org
Subject: Re: [PATCH v2 00/40] tracing: Inter-event (e.g. latency) support

Hi Steve,

On Tue, 2017-09-19 at 12:31 -0400, Steven Rostedt wrote:
> On Tue,  5 Sep 2017 16:57:12 -0500
> Tom Zanussi <tom.zanussi@...ux.intel.com> wrote:
> 
> > Hi,
> > 
> > This is V2 of the inter-event tracing patchset.
> > 
> 
> Hi Tom,
> 
> I was wondering if you had a v3 ready? I would like to get it into the
> next merge window, but I would also like it to be in linux-next early,
> which means we need the next version rather soon (hopefully that will
> be the last version).
> 

Yeah, it's almost ready.  At this point, I've addressed all the comments
except for:

 - PATCH v2 25/40] tracing: Add support for dynamic tracepoints

 which I need to do a little bit of research on to figure out what
exactly I need to do there.

I was also kind of looking for a couple patches from you to fold in
which you had mentioned you were going to send for:

 -  [PATCH v2 35/40] tracing: Reverse the order event_mutex/trace_types_lock are taken
 -  [PATCH v2 40/40] tracing: Add trace_event_buffer_reserve() variant that allows recursion

I've been using the trace_recursive_lock() patch you posted in place of
the latter and it's working fine.  :-)

Tom

> -- Steve


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ