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: <20120206202722.GA556@aftab>
Date:	Mon, 6 Feb 2012 21:27:22 +0100
From:	Borislav Petkov <bp@...64.org>
To:	Peter Zijlstra <peterz@...radead.org>
Cc:	Stephane Eranian <eranian@...gle.com>,
	linux-kernel@...r.kernel.org, acme@...hat.com, mingo@...e.hu,
	robert.richter@....com, eric.dumazet@...il.com,
	Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: [BUG] perf: perf sched warning possibly due to clock granularity
 on AMD

On Mon, Feb 06, 2012 at 05:54:19PM +0100, Peter Zijlstra wrote:
> On Mon, 2012-02-06 at 17:46 +0100, Borislav Petkov wrote:
> > > across all CPUs in the entire system.
> > 
> > Right, by the "entire system" you mean consistent across cores and
> > sockets but not necessarily across cabinets, as in the comment above,
> > correct?
> > 
> > If so, let me ask around if this holds true too.
> 
> Every CPU available to the kernel. So if you run a single system image
> across your cabinets, then yes those too.

Ok, but what about that sentence "(but not across cabinets - we turn
it off in that case explicitly.)" - I don't see any place where it is
turned off explicitly... Maybe a stale comment?

-- 
Regards/Gruss,
Boris.

Advanced Micro Devices GmbH
Einsteinring 24, 85609 Dornach
GM: Alberto Bozzo
Reg: Dornach, Landkreis Muenchen
HRB Nr. 43632 WEEE Registernr: 129 19551
--
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