From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [GIT PULL] Native Linux KVM tool for 3.1 Date: Mon, 25 Jul 2011 11:35:52 +0300 Message-ID: <4E2D2AE8.7050100@redhat.com> References: <4E2CA6DE.4040900@web.de> <20110725075305.GA32294@elte.hu> <0EAA5203-D598-4CBA-B8D2-AB371A7689A9@suse.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: Pekka Enberg , Ingo Molnar , Jan Kiszka , torvalds@linux-foundation.org, akpm@linux-foundation.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org, gorcunov@gmail.com, levinsasha928@gmail.com, asias.hejun@gmail.com, prasadjoshi124@gmail.com To: Alexander Graf Return-path: Received: from mx1.redhat.com ([209.132.183.28]:30598 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750864Ab1GYIgO (ORCPT ); Mon, 25 Jul 2011 04:36:14 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 07/25/2011 11:31 AM, Alexander Graf wrote: > In Ingo's reasoning, the next step would be to rewrite glibc and put it into the kernel tree, because we end up adding syscalls so adding them to the in-kernel libc with the same commit would be a lot easier and cleaner. 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. -- error compiling committee.c: too many arguments to function