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: <3889bf3ab66bbb35ea239b63d95cc4c4.squirrel@www.firstfloor.org>
Date:	Sun, 21 Nov 2010 17:52:14 +0100
From:	"Andi Kleen" <andi@...stfloor.org>
To:	"Stephane Eranian" <eranian@...gle.com>
Cc:	"Andi Kleen" <andi@...stfloor.org>,
	"Lin Ming" <ming.m.lin@...el.com>,
	"Peter Zijlstra" <a.p.zijlstra@...llo.nl>,
	"Ingo Molnar" <mingo@...e.hu>,
	"lkml" <linux-kernel@...r.kernel.org>,
	"Frederic Weisbecker" <fweisbec@...il.com>,
	"Arjan van de Ven" <arjan@...radead.org>
Subject: Re: [RFC PATCH 3/3 v2] perf: Update perf tool to monitor uncore
 events


>>
>> In fact I suspect uncore events are only really useful
>> with "stat", but not with "top", or if they are used in top
>> then the symbol reporting should be disabled.
>>
> I agree, uncore should only be used for counting on a
> per-cpu basis. You can leave the perf tool as is, but

I think you mean per socket base, right? per cpu (= cpu core thread)
doesn't make sense for the uncore either.

Per socket would need a new command line mode. The new mode should
never report any symbols or processes, just events per socket.

-Andi

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