linux-kernel - Re: [tip:perf/core] perf/x86: Fix active

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CABPqkBTjzwjB9m_5jAjHV=iNuwt3os44p=SSxs7pT7PwmJ+Khw@mail.gmail.com>
Date:	Mon, 13 Jan 2014 16:49:01 +0100
From:	Stephane Eranian <eranian@...gle.com>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Ingo Molnar <mingo@...nel.org>, "H. Peter Anvin" <hpa@...or.com>,
	LKML <linux-kernel@...r.kernel.org>,
	Thomas Gleixner <tglx@...utronix.de>,
	"linux-tip-commits@...r.kernel.org" 
	<linux-tip-commits@...r.kernel.org>
Subject: Re: [tip:perf/core] perf/x86: Fix active_entry initialization

On Mon, Jan 13, 2014 at 4:45 PM, Peter Zijlstra <peterz@...radead.org> wrote:
>
> On Sun, Jan 12, 2014 at 10:42:47AM -0800, tip-bot for Stephane Eranian wrote:
> > -     union {
> > -             struct hlist_node       hlist_entry;
> > -             struct list_head        active_entry;
> > -     };
> > +     struct hlist_node               hlist_entry;
> > +     struct list_head                active_entry;
>
> Fwiw, we could probably stick both of those in hw_perf_event.
>
> the software event's hrtimer isn't the biggest entry anymore, so we
> could add the hlist_entry in there, and we can start a new entry for
> RAPL events.

Yeah, that would be possible.
The other thing I noticed too in another uncore patch I am preparing is
that we could also use that active_entry to avoid tracking association
of uncore events to counters to update them in the hrtimer routine.
All we need there is the list of active event on the uncore PMU and
we iterate over them.
--
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/