linux-kernel - Re: [PATCH 2/11] Sched clock paravirt op

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <45C9125A.3040704@vmware.com>
Date:	Tue, 06 Feb 2007 15:42:18 -0800
From:	Zachary Amsden <zach@...are.com>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
CC:	Andi Kleen <ak@....de>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...l.org>,
	Rusty Russell <rusty@...tcorp.com.au>,
	Chris Wright <chrisw@...s-sol.org>
Subject: Re: [PATCH 2/11] Sched clock paravirt op

Jeremy Fitzhardinge wrote:
> Zachary Amsden wrote:
>   
>> Scheduled (or available) time and real time are good notions.  Stolen
>> time is debatable.  But TSC is basically just always wrong.  That's
>> why I don't want to overload the rdtsc operation. 
>>     
> Well, in the Xen case it is actually guaranteed to be correct and useful
> as real time, but that's definitely not something we can expect in
> general.  But you're talking specifically about schedulable vcpu time
> here, right?
>   

Not schedulable time, scheduled time (schedulable - scheduled) = stolen

Zach

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