linux-kernel - Re: Stolen and degraded time and schedulers

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: <45FACB8E.7000505@goop.org>
Date:	Fri, 16 Mar 2007 09:53:34 -0700
From:	Jeremy Fitzhardinge <jeremy@...p.org>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Dan Hecht <dhecht@...are.com>, dwalker@...sta.com,
	cpufreq@...ts.linux.org.uk,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Con Kolivas <kernel@...ivas.org>,
	Chris Wright <chrisw@...s-sol.org>,
	Virtualization Mailing List <virtualization@...ts.osdl.org>,
	john stultz <johnstul@...ibm.com>,
	Thomas Gleixner <tglx@...utronix.de>, paulus@...ibm.com,
	schwidefsky@...ibm.com, Rik van Riel <riel@...hat.com>
Subject: Re: Stolen and degraded time and schedulers

Ingo Molnar wrote:
> i dont understand: how are you separating 'stolen time' drifts from 
> events generated for absolute timeouts?
>   

I'm not sure what you're asking; I think we're talking past each other.

I can extract from Xen how much time was stolen over some real-time
interval.  If I call do_stolen_accounting() at any two arbitrary points,
it will compute the amount of time stolen in the interval.  So that
means I can call it from time to time to update stolen time.  Of course,
this accounting will be out of date for a while, but it doesn't matter
too much.  I call it from the timer interrupt, since it will be called
occasionally on idle CPUs and often on busy CPUs, which is what we want.

Oh, its worth pointing out that stolen time is accounted against CPUs
rather than individual processes, so it doesn't need to be related to
process scheduling.

Also, none of this is in the patch set I posted; I've implemented it
since, and it will be in the next batch.

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