[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200916173845.GA3072065@kroah.com>
Date: Wed, 16 Sep 2020 19:38:45 +0200
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Frankie Chang <Frankie.Chang@...iatek.com>
Cc: Todd Kjos <tkjos@...gle.com>,
Joel Fernandes <joel@...lfernandes.org>,
Martijn Coenen <maco@...roid.com>,
Arve Hjønnevåg <arve@...roid.com>,
Christian Brauner <christian@...uner.io>,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
wsd_upstream@...iatek.com, Jian-Min Liu <Jian-Min.Liu@...iatek.com>
Subject: Re: [PATCH v9 3/3] binder: add transaction latency tracer
On Tue, Sep 08, 2020 at 10:06:48PM +0800, Frankie Chang wrote:
> +#if IS_ENABLED(CONFIG_BINDER_TRANSACTION_LATENCY_TRACKING)
> +#include <linux/rtc.h>
> +#include <linux/time.h>
> +#endif
> +
> struct binder_context {
> struct binder_node *binder_context_mgr_node;
> struct mutex context_mgr_node_lock;
> @@ -524,6 +529,14 @@ struct binder_transaction {
> * during thread teardown
> */
> spinlock_t lock;
> + /**
> + * @ts and @real_ts are used to record the time
> + * that the binder transaction startup
> + */
> +#if IS_ENABLED(CONFIG_BINDER_TRANSACTION_LATENCY_TRACKING)
> + struct timespec64 ts;
> + struct timespec64 real_ts;
Why isn't this ktime_t? Is timespec64 really something to be using
still?
thanks,
greg k-h
Powered by blists - more mailing lists