mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jin, Yao" <yao.jin@linux.intel.com>
To: Milian Wolff <milian.wolff@kdab.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] perf report: Make --branch-history work without callgraphs(-g) option in perf record
Date: Fri, 5 May 2017 11:10:24 +0800	[thread overview]
Message-ID: <c660953f-02c9-1da5-069d-cd75a8ae62f4@linux.intel.com> (raw)
In-Reply-To: <21042314.DNPhWqAGjE@milian-kdab2>

SNIP
>> -		if (symbol_conf.use_callchain) {
>> +		if (symbol_conf.use_callchain &&
>> +			!symbol_conf.show_branchflag_count) {
>>   			ui__error("Selected -g or --branch-history but no "
>>   				  "callchain data. Did\n"
>>   				  "you call 'perf record' without -g?\n");
> The `--branch-history` part of this error message is now stale, no?

Yes, the error message is obsolete. I will change it in next version.
>
>> @@ -397,7 +398,8 @@ static int perf_evlist__tty_browse_hists(struct
>> perf_evlist *evlist,
>>
>>   		hists__fprintf_nr_sample_events(hists, rep, evname, stdout);
>>   		hists__fprintf(hists, !quiet, 0, 0, rep->min_percent, stdout,
>> -			       symbol_conf.use_callchain);
>> +			       symbol_conf.use_callchain |
>> +			       symbol_conf.show_branchflag_count);
>>   		fprintf(stdout, "\n\n");
>>   	}
> Not sure about the coding style here, but shouldn't this be a boolean or
> operator here '||' - semantically? Functionality wise it will be the same, I
> guess?

Should be same. While I will follow your comments to change it to '||'.

I will wait other comments for some days and then send out the next version.

Thanks
Jin Yao

      reply	other threads:[~2017-05-05  3:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-04  8:31 Jin Yao
2017-05-04  8:58 ` Milian Wolff
2017-05-05  3:10   ` Jin, Yao [this message]

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=c660953f-02c9-1da5-069d-cd75a8ae62f4@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=kan.liang@intel.com \
    --cc=milian.wolff@kdab.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

Powered by JetHome