linux-kernel - Re: [RFC][PATCH 1/3] perf: Tighten (and fix) the grouping condition

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: <20150204125954.GL21418@twins.programming.kicks-ass.net>
Date:	Wed, 4 Feb 2015 13:59:54 +0100
From:	Peter Zijlstra <peterz@...radead.org>
To:	Mark Rutland <mark.rutland@....com>
Cc:	"mingo@...nel.org" <mingo@...nel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"vincent.weaver@...ne.edu" <vincent.weaver@...ne.edu>,
	"eranian@...il.com" <eranian@...il.com>,
	"jolsa@...hat.com" <jolsa@...hat.com>,
	"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
	"tglx@...utronix.de" <tglx@...utronix.de>
Subject: Re: [RFC][PATCH 1/3] perf: Tighten (and fix) the grouping condition

On Fri, Jan 23, 2015 at 03:22:57PM +0000, Mark Rutland wrote:
> > > It seems this would still allow you to group CPU-affine software and
> > > uncore events, which also doesn't make sense: the software events will
> > > count on a single CPU while the uncore events aren't really CPU-affine.
> > > 
> > > Which isn't anything against this patch, but probably something we
> > > should tighten up too.
> > 
> > Indeed, that would need a wee bit of extra infrastructure though; as we
> > cannot currently distinguish between regular cpuctx and uncore like
> > things.
> 
> Isn't the event->pmu->task_ctx_nr sufficient, as with how we identify
> software events?
> 
> Or am I making some completely bogus assumptions in the diff below?

>  	/*
> +	 * System-wide (A.K.A. "uncore") events cannot be associated with a
> +	 * particular CPU, and hence cannot be associated with a particular
> +	 * task either. It's non-sensical to group them with other event types,
> +	 * which are CPU or task bound.
> +	 */

So I think we want to allow grouping software events with say uncore
events; if you start them both out on the same 'cpu'
perf_pmu_migrate_context() would move the software event along with it.

The use case is for non-sampling uncores, where if you have a software
leader you can still get a periodic samples. Clearly looking at task
state or the like is pointless, but PERF_SAMPLE_READ is useful to record
values at regular intervals into the buffer.

But yes, I think ctx_nr might just do.
--
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/