[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090703093032.GI3902@elte.hu>
Date: Fri, 3 Jul 2009 11:30:32 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jaswinder Singh Rajput <jaswinder@...nel.org>
Cc: Arjan van de Ven <arjan@...radead.org>,
Paul Mackerras <paulus@...ba.org>,
Benjamin Herrenschmidt <benh@...nel.crashing.org>,
Anton Blanchard <anton@...ba.org>,
Thomas Gleixner <tglx@...utronix.de>,
Peter Zijlstra <peterz@...radead.org>,
x86 maintainers <x86@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>
Subject: Re: [PATCH 1/2 -tip] perf_counter: Add generalized hardware
vectored co-processor support for AMD and Intel Corei7/Nehalem
* Jaswinder Singh Rajput <jaswinder@...nel.org> wrote:
> > $ ./perf list shows vector events like :
> >
> > vec-adds OR add [Hardware vector event]
> > vec-muls OR multiply [Hardware vector event]
> > vec-divs OR divide [Hardware vector event]
> > vec-idle-cycles OR vec-empty-cycles [Hardware vector event]
> > vec-stall-cycles OR vec-busy-cycles [Hardware vector event]
> > vec-ops OR vec-operations [Hardware vector event]
btw., why does this printout SHOUT the 'or'? It's certainly not an
important piece of information. Something like:
vec-adds | add [Hardware vector event]
vec-muls | multiply [Hardware vector event]
vec-divs | divide [Hardware vector event]
vec-idle-cycles | vec-empty-cycles [Hardware vector event]
vec-stall-cycles | vec-busy-cycles [Hardware vector event]
vec-ops | vec-operations [Hardware vector event]
looks better on all levels.
Ingo
--
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