From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [ANNOUNCE] kvm-14 release Date: Mon, 05 Mar 2007 10:52:43 +0200 Message-ID: <45EBDA5B.1070105@qumranet.com> References: <45D98390.6060001@qumranet.com> <20070219131633.GF31525@redhat.com> <45D9A464.8040406@qumranet.com> <45D9C57D.9030203@qumranet.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel Return-path: In-Reply-To: <45D9C57D.9030203-atKUWr5tajBWk0Htik3J/w@public.gmane.org> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org Avi Kivity wrote: > James Morris wrote: >> It's traditional for the mainline kernel to maintain backward >> compatibility with existing userspace ABIs (e.g. syscalls). >> >> The idea of a userspace application breaking because of a mainline >> kernel upgrade is not acceptable to users and also pretty much >> unsupportable by distros. >> > > That is of course very true, and it is a goal of kvm to have a stable > userspace interface. I plan to target 2.6.21 as the stable ABI release. > As the alert reader will have guessed, this is now postponed to 2.6.22. I will provide a nonintrusive patch backporting the stable ABI to 2.6.21 if desired. -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV