linux-kernel - Re: [PATCH 1/2] 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] [thread-next>] [day] [month] [year] [list]

Message-Id: <1184217293.6005.754.camel@localhost.localdomain>
Date:	Thu, 12 Jul 2007 15:14:53 +1000
From:	Rusty Russell <rusty@...tcorp.com.au>
To:	Avi Kivity <avi@...ranet.com>
Cc:	kvm-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org,
	Ingo Molnar <mingo@...e.hu>, shaohua.li@...el.com
Subject: Re: [PATCH 1/2] SCHED: Generic hooks for trapping task preemption

On Wed, 2007-07-11 at 18:55 +0300, Avi Kivity wrote:
> +	fire_sched_out_preempt_hooks(current);
>    	prepare_lock_switch(rq, next);
>  	prepare_arch_switch(next);

Damn, I just found a use for this in lguest.

Any chance of handing "next" to the sched_out hook so we can optimize
the lguest <-> lguest switch?

FYI, lguest turns off PGE globally when you load the module, because
turning it off on each guest entry v. slow.  With these hooks I can be
far smarter...

Thanks!
Rusty.


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