linux-kernel - Re: [patch] paravirt: VDSO page is essential

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: <45EC24CA.1020707@qumranet.com>
Date:	Mon, 05 Mar 2007 16:10:18 +0200
From:	Avi Kivity <avi@...ranet.com>
To:	Ingo Molnar <mingo@...e.hu>
CC:	Andi Kleen <ak@...e.de>, Andrew Morton <akpm@...ux-foundation.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel@...r.kernel.org, Roland McGrath <roland@...hat.com>,
	Rusty Russell <rusty@...tcorp.com.au>
Subject: Re: [patch] paravirt: VDSO page is essential

Ingo Molnar wrote:
> * Andi Kleen <ak@...e.de> wrote:
>
>   
>> I think we would need to have a paravirt ops callback to decide this 
>> first. But it doesn't look critical to me anyways.
>>     
>
> well, it's critical to me in two ways: 1) to make the i386 paravirt code 
> clean 2) to have a proper VDSO for a KVM paravirtual guest. The original 
> change is also bad because it changes how a Linux guest behaves: it 
> turns off the vdso by default, and disables the compat VDSO. I.e. it's a 
> bad performance step backwards if CONFIG_PARAVIRT is enabled (uses int 
> $0x80 instead of sysenter), which hurts only KVM and basically none of 
> the other hypervisors. It also muddifies the VDSO picture wrt. 
> virtualization.
>
>   

kvm paravirt is only used by developers at this time.  I don't have a 
problem with solving this in the 2.6.22 timeframe.

-- 
error compiling committee.c: too many arguments to function

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