linux-kernel - Re: [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal time.

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] [day] [month] [year] [list]

Message-ID: <50B3CA73.5090205@linux.vnet.ibm.com>
Date:	Mon, 26 Nov 2012 14:00:51 -0600
From:	Michael Wolf <mjw@...ux.vnet.ibm.com>
To:	Rik van Riel <riel@...hat.com>
CC:	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	peterz@...radead.org, mtosatti@...hat.com, glommer@...allels.com,
	mingo@...hat.com, avi@...hat.com, anthony@...emonkey.ws
Subject: Re: [PATCH RFC V2 0/5] Separate consigned (expected steal) from steal
 time.

On 10/22/2012 10:33 AM, Rik van Riel wrote:
> On 10/16/2012 10:23 PM, Michael Wolf wrote:
>> In the case of where you have a system that is running in a
>> capped or overcommitted environment the user may see steal time
>> being reported in accounting tools such as top or vmstat.  This can
>> cause confusion for the end user.
>
> How do s390 and Power systems deal with reporting that kind
> of information?
>
> IMHO it would be good to see what those do, so we do not end
> up re-inventing the wheel, and confusing admins with yet another
> way of reporting the information...
>
Sorry for the delay in the response.  I'm assuming you are asking about 
s390 and Power lpars.
In the case of lpar on POWER systems they simply report steal time and 
do not alter it in any way.
They do however report how much processor is assigned to the partition 
and that information is
in /proc/ppc64/lparcfg.

Mike

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