public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Jiri Olsa <jolsa@redhat.com>
Cc: acme@kernel.org, jolsa@kernel.org, peterz@infradead.org,
	mingo@redhat.com, alexander.shishkin@linux.intel.com,
	Linux-kernel@vger.kernel.org, ak@linux.intel.com,
	kan.liang@intel.com, yao.jin@intel.com
Subject: Re: [PATCH v2 04/10] perf util: Add rbtree node_delete ops
Date: Tue, 28 Nov 2017 20:19:33 +0800	[thread overview]
Message-ID: <5ce197f9-4a5b-cbc7-e407-716396aea8b8@linux.intel.com> (raw)
In-Reply-To: <20171128111228.GC2732@krava>



On 11/28/2017 7:12 PM, Jiri Olsa wrote:
> On Mon, Nov 27, 2017 at 10:07:24PM +0800, Jin Yao wrote:
>> In current stat-shadow.c, the rbtree deleting is ignored.
>>
>> The patch reconstructs the code of rblist init/free, and adds
>> the implementation to node_delete method of rblist.
>>
>> Signed-off-by: Jin Yao <yao.jin@linux.intel.com>
>> ---
>>   tools/perf/util/stat-shadow.c | 33 +++++++++++++++++++++++++++++----
>>   tools/perf/util/stat.h        |  3 +++
>>   2 files changed, 32 insertions(+), 4 deletions(-)
>>
>> diff --git a/tools/perf/util/stat-shadow.c b/tools/perf/util/stat-shadow.c
>> index c53b80d..0fdd2aa 100644
>> --- a/tools/perf/util/stat-shadow.c
>> +++ b/tools/perf/util/stat-shadow.c
>> @@ -40,6 +40,7 @@ static struct stats runtime_aperf_stats[NUM_CTX][MAX_NR_CPUS];
>>   static struct rblist runtime_saved_values;
>>   static bool have_frontend_stalled;
>>   
>> +struct runtime_stat rt_stat;
>>   struct stats walltime_nsecs_stats;
>>   
>>   struct saved_value {
>> @@ -103,6 +104,18 @@ static struct rb_node *saved_value_new(struct rblist *rblist __maybe_unused,
>>   	return &nd->rb_node;
>>   }
>>   
>> +static void saved_value_delete(struct rblist *rblist __maybe_unused,
>> +			       struct rb_node *rb_node)
>> +{
>> +	struct saved_value *v;
>> +
>> +	BUG_ON(!rb_node);
>> +	v = container_of(rb_node,
>> +			 struct saved_value,
>> +			 rb_node);
> 
> any reason for this to be cut on 3 lines? single line wouldn't cross 80 chars length..
> 
> jirka
> 

Oh, yes, one line is enough. I will fix that.

Thanks
Jin Yao

  reply	other threads:[~2017-11-28 12:19 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-27 14:07 [PATCH v2 00/10] perf stat: Enable '--per-thread' on all threads Jin Yao
2017-11-27 14:07 ` [PATCH v2 01/10] perf util: Create rblist__reset() function Jin Yao
2017-11-27 14:07 ` [PATCH v2 02/10] perf util: Define a structure for runtime shadow metrics stats Jin Yao
2017-11-27 14:07 ` [PATCH v2 03/10] perf util: Extend rbtree to support shadow stats Jin Yao
2017-11-27 14:07 ` [PATCH v2 04/10] perf util: Add rbtree node_delete ops Jin Yao
2017-11-28 11:12   ` Jiri Olsa
2017-11-28 12:14     ` Jin, Yao
2017-11-28 11:12   ` Jiri Olsa
2017-11-28 12:19     ` Jin, Yao [this message]
2017-11-27 14:07 ` [PATCH v2 05/10] perf util: Update and print per-thread shadow stats Jin Yao
2017-11-27 14:07 ` [PATCH v2 06/10] perf util: Remove a set of shadow stats static variables Jin Yao
2017-11-27 14:07 ` [PATCH v2 07/10] perf stat: Allocate shadow stats buffer for threads Jin Yao
2017-11-28 11:12   ` Jiri Olsa
2017-11-28 12:23     ` Jin, Yao
2017-11-27 14:07 ` [PATCH v2 08/10] perf util: Reuse thread_map__new_by_uid to enumerate threads from /proc Jin Yao
2017-11-27 14:07 ` [PATCH v2 09/10] perf stat: Remove --per-thread pid/tid limitation Jin Yao
2017-11-27 14:07 ` [PATCH v2 10/10] perf stat: Resort '--per-thread' result Jin Yao

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=5ce197f9-4a5b-cbc7-e407-716396aea8b8@linux.intel.com \
    --to=yao.jin@linux.intel.com \
    --cc=Linux-kernel@vger.kernel.org \
    --cc=acme@kernel.org \
    --cc=ak@linux.intel.com \
    --cc=alexander.shishkin@linux.intel.com \
    --cc=jolsa@kernel.org \
    --cc=jolsa@redhat.com \
    --cc=kan.liang@intel.com \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=yao.jin@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox