From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [patch 37/43] lguest: Virtio helper routines for a descriptor ringbuffer implementation Date: Tue, 02 Oct 2007 08:02:33 +0200 Message-ID: <4701DEF9.6070707@qumranet.com> References: <20070926063618.956228976@rustcorp.com.au> <20070926063651.769960367@rustcorp.com.au> <46FFD6CB.9020904@qumranet.com> <1191240202.6648.11.camel@localhost.localdomain> <4700E45E.6080505@qumranet.com> <1191298867.6979.60.camel@localhost.localdomain> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1191298867.6979.60.camel@localhost.localdomain> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: virtualization-bounces@lists.linux-foundation.org Errors-To: virtualization-bounces@lists.linux-foundation.org To: Rusty Russell Cc: lguest@ozlabs.org, Dor Laor , virtualization@lists.linux-foundation.org List-Id: virtualization@lists.linuxfoundation.org Rusty Russell wrote: > On Mon, 2007-10-01 at 14:13 +0200, Avi Kivity wrote: > >> Rusty Russell wrote: >> >>> Yes, but this is what lguest is for, to play without fixing an ABI. I >>> fully expect incompatible tweaks before KVM causes the ABI to nail down. >>> >> I'm worried about users tearing down the "caution, experimental ABI, >> will invalidate warranty" sticker from the package, selecting >> CONFIG_EXPERIMENTAL, CONFIG_I_REALLY_MEAN_ITS_EXPERIMENTAL, and >> CONFIG_I_DONT_CARE_IF_THIS_BLOWS_UP, not reading your blog, and running >> 2.6.24 guests on top of 2.6.25 or vice versa. >> >> I want the module not to load instead of the guest blowing up. >> > > Well, this is the guest side we're talking about. We can use some bogus > vendor ID for the experimental devices so that they simply won't be > found by the final drivers. > > That works. Thanks! -- Any sufficiently difficult bug is indistinguishable from a feature.