linux-kernel - Re: [GIT PULL] Native Linux KVM tool for 3.1

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: <4E2D862C.10204@redhat.com>
Date:	Mon, 25 Jul 2011 18:05:16 +0300
From:	Avi Kivity <avi@...hat.com>
To:	Joerg Roedel <joro@...tes.org>
CC:	Alexander Graf <agraf@...e.de>, Pekka Enberg <penberg@...nel.org>,
	Ingo Molnar <mingo@...e.hu>, Jan Kiszka <jan.kiszka@....de>,
	torvalds@...ux-foundation.org, akpm@...ux-foundation.org,
	linux-kernel@...r.kernel.org, kvm@...r.kernel.org,
	gorcunov@...il.com, levinsasha928@...il.com, asias.hejun@...il.com,
	prasadjoshi124@...il.com
Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1

On 07/25/2011 04:10 PM, Joerg Roedel wrote:
> >  That actually makes a ton of sense.  One immediate win would be that
> >  klibc can be tuned to the kernel it ships with (the dynamic loader will
> >  pick the correct object), so less #ifdef trees.  Another would be to
> >  make klibc the formal kernel interface, which allows us to reimplement
> >  an older interface in terms of the one that supercedes it.
>
> A libc in the kernel tree would indeed make a lot of sense and I am all
> for it :) It would also help to get new interfaces to the users faster.
> But it should probably not be the primary exported interface. This would
> just move the compatability problem from the kernel into user-space.

It's a better place for it, IMO.  For example, if we dump xnotify in 
favour of ynotify, we can implement xnotify using ynotify in klibc, and 
so avoid increasing the kernel's footprint.  As another example, there's 
an OS that implements its 32-bit ABI in userspace.

(of course that only works for new interfaces; the old ones have to be 
implemented in the kernel unless we thunk them somehow)

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