linux-kernel - [PATCH 0/2][RFC] Scheduler preemption hooks, #2

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

Message-Id: <11841693332609-git-send-email-avi@qumranet.com>
Date:	Wed, 11 Jul 2007 18:55:31 +0300
From:	Avi Kivity <avi@...ranet.com>
To:	kvm-devel@...ts.sourceforge.net
Cc:	linux-kernel@...r.kernel.org, Ingo Molnar <mingo@...e.hu>,
	shaohua.li@...el.com, rusty@...tcorp.com.au
Subject: [PATCH 0/2][RFC] Scheduler preemption hooks, #2

I redid the the scheduler preemption patches based on Rusty's feedback.
Things do look much cleaner this time around.

Changes:
- split into core and kvm parts
- incorporated Shaohua Li's fix
- each task now has a list of independently managed preemption hooks
- move preempt hook pointer to a hot cache line within task_struct

I haven't made kernel_fpu_begin()/kernel_fpu_end() preemptible as promised,
because (a) we need to find a place to put the fpu state, and (b) we should
get better performance by reusing cr0.ts anyway.

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