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: <20150512130421.GB29215@kernel.org>
Date:	Tue, 12 May 2015 10:04:21 -0300
From:	Arnaldo Carvalho de Melo <acme@...nel.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	"Liang, Kan" <kan.liang@...el.com>, Ingo Molnar <mingo@...nel.org>,
	Stephane Eranian <eranian@...gle.com>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH V9 8/8] perf tools: handle PERF_RECORD_LOST_SAMPLES

Em Tue, May 12, 2015 at 02:43:44PM +0200, Peter Zijlstra escreveu:
> On Mon, May 11, 2015 at 06:27:58PM -0300, Arnaldo Carvalho de Melo wrote:
> > I disagree, since the support is there, we need to have it in
> > hists->events_stats[PERF_RECORD_LOST_SAMPLES].

> > But that can be done in a follow up patch.

> Agreed, it would be good to know of which event the samples got lost.

> > It just came quickly to my attention because of all the discussion about
> > where to store something (PERF_SAMPLE_ID via sample_type + sample_id_all)
> > that doesn't get used in the patch that introduces it :-)
> > 
> > I'll try to test this all tomorrow and will try to do the needed wiring
> > to hists_evsel->hists->events_stats.
> > 
> > All working I can push this all via my perf/core event, if PeterZ
> > agrees and is ok with the kernel specific bits.
> 
> I would like to carry these as there some conflicts with other patches I
> have.

So go ahead and do it, when it lands on tip I'll check and try to
continue what was discussed here, thanks!

- 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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ