linux-kernel - Re: [PATCH] perf_events: improve x86 event scheduling (v5)

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: <20100121120224.GE5017@nowhere>
Date:	Thu, 21 Jan 2010 13:02:26 +0100
From:	Frederic Weisbecker <fweisbec@...il.com>
To:	Stephane Eranian <eranian@...gle.com>
Cc:	Peter Zijlstra <peterz@...radead.org>,
	linux-kernel@...r.kernel.org, mingo@...e.hu, paulus@...ba.org,
	davem@...emloft.net, perfmon2-devel@...ts.sf.net, eranian@...il.com
Subject: Re: [PATCH] perf_events: improve x86 event scheduling (v5)

On Thu, Jan 21, 2010 at 12:44:03PM +0100, Stephane Eranian wrote:
> > If the scheduling validation fails, then you just need to rollback
> > the whole group.
> >
> > That's sensibly what you did in your patch, right? Except the loop
> > is now handled by the core code.
> >
> >
> Ok, I think I missed where you were actually placing that loop.
> So you want to do this in group_sched_in(), right?



Exactly!


 
> >
> > I don't understand why that can't be done with the above model.
> > In your patch we iterate through the whole group, collect events,
> > and schedule them.
> >
> > With the above, the collection is just done on enable(), and the scheduling
> > is done with the new pmu callbacks.
> >
> > The thing is sensibly the same, where is the obstacle?
> >
> There is none. You've just hoisted the some of the code from
> hw_perf_group_sched_in().


Exactly :)

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