linux-kernel - RE: [PATCH V2 1/3] perf,tools: get correct cpu id for print

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]

Date:	Fri, 28 Aug 2015 14:39:21 +0000
From:	"Liang, Kan" <kan.liang@...el.com>
To:	"acme@...nel.org" <acme@...nel.org>
CC:	Jiri Olsa <jolsa@...hat.com>,
	"jolsa@...nel.org" <jolsa@...nel.org>,
	"ak@...ux.intel.com" <ak@...ux.intel.com>,
	"namhyung@...nel.org" <namhyung@...nel.org>,
	"eranian@...gle.com" <eranian@...gle.com>,
	"Hunter, Adrian" <adrian.hunter@...el.com>,
	"dsahern@...il.com" <dsahern@...il.com>,
	"a.p.zijlstra@...llo.nl" <a.p.zijlstra@...llo.nl>,
	"mingo@...hat.com" <mingo@...hat.com>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH V2 1/3] perf,tools: get correct cpu id for print_aggr

> 
> Em Fri, Aug 28, 2015 at 01:33:22PM +0000, Liang, Kan escreveu:
> > > On Thu, Jul 02, 2015 at 03:08:43AM -0400, kan.liang@...el.com wrote:
> > > > From: Kan Liang <kan.liang@...el.com> print_aggr fails to print
> > > > per-core/per-socket statistics after commit 582ec0829b3d ("perf
> > > > stat: Fix per-socket output bug for uncore
> > > > events") if events have differnt cpus. Because in print_aggr,
> > > > aggr_get_id needs index (not cpu id) to find core/pkg id. Also,
> > > > evsel cpu maps should be used to get aggregated id.
> > > > Signed-off-by: Kan Liang <kan.liang@...el.com>
> 
> > > Acked-by: Jiri Olsa <jolsa@...nel.org>
> 
> > Hi Arnaldo,
> 
> > Could you please merge this patch?
> > This patch is to fix a bug of perf stat. It doesn't depend on other
> > patches of the patchset, and can be merged by itself.
> 
> Right, in such cases, please, make it clear against which branch this should
> be applied, i.e. if this is a longstanding bug that needs to go to perf/urgent,
> i.e. to the current merge window, ASAP, or if this is for something that was
> introduced in the current development branch, perf/core.
> 
> In this case it needs to go to perf/urgent, where it applies cleanly,
> perf/core has extra stuff there that fuzzes a bit.
> 
> Also, since you know the cset where this bug was introduced, please
> consider adding a "Fixes:" tag, commom everywhere in the kernel:

OK. I think this patch needs to go to perf/urgent.
Should I re-send this patch with "Fixes:" tag and comments? 

Thanks,
Kan
> 
>   [acme@zoo linux]$ git log | grep '^[ \t]\+Fixes:'  | wc -l
>   3805
> 
> And we use it in tools/, sometime I add it while editing changelogs, like in
> this patch:
> 
>   [acme@zoo linux]$ git log tools/ | grep '^[ \t]\+Fixes:' | head -5
>     Fixes: 582ec0829b3d ("perf stat: Fix per-socket output bug for uncore
> events")
>     Fixes: b685ac22b436 ("perf symbols: Add front end cache for DSO symbol
> lookup")
>     Fixes: 06b234ec26fd ("perf script: Don't assume evsel position of tracking
> events")
>     Fixes: d4957633bf9d ("perf report: Add infrastructure for a cycles
> histogram")
>     Fixes: 75186a9b09e4 ("perf probe: Fix to show lines of sys_ functions
> correctly")
>   [acme@zoo linux]$
> 
> - Arnaldo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/