linux-kernel - Re: [PATCH 1/3] SCHED: Generic hooks for trapping task preemption

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]

Date:	Wed, 25 Jul 2007 16:13:55 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	shaohua.li@...el.com, rusty@...tcorp.com.au,
	Andi Kleen <ak@...e.de>
Subject: Re: [PATCH 1/3] SCHED: Generic hooks for trapping task preemption

Ingo Molnar wrote:
> * Ingo Molnar <mingo@...e.hu> wrote:
>
>   
>>> This adds a general mechanism whereby a task can request the 
>>> scheduler to notify it whenever it is preempted or scheduled back 
>>> in.  This allows the task to swap any special-purpose registers like 
>>> the fpu or Intel's VT registers.
>>>       
>> ok, this looks very clean, i've added it to my scheduler tree. You've 
>> tested this with KVM, on both 32-bit and 64-bit, correct?
>>     
>
> note: i've done a hook -> notifier rename - 'hook' is way too generic 
> sounding and also slightly loaded. (updated patch below)
>
>   

Okay, both i386 and x86_64 are happy (with the missing 'next' argument
added, but with the old hook name).

-- 
Do not meddle in the internals of kernels, for they are subtle and quick to panic.

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