From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MFkbU-00084u-R6 for qemu-devel@nongnu.org; Sun, 14 Jun 2009 03:58:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MFkbQ-00080p-Vf for qemu-devel@nongnu.org; Sun, 14 Jun 2009 03:58:12 -0400 Received: from [199.232.76.173] (port=34403 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MFkbQ-00080X-Nu for qemu-devel@nongnu.org; Sun, 14 Jun 2009 03:58:08 -0400 Received: from mx2.redhat.com ([66.187.237.31]:55209) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MFkbQ-0004zH-7L for qemu-devel@nongnu.org; Sun, 14 Jun 2009 03:58:08 -0400 Message-ID: <4A34AD04.7080701@redhat.com> Date: Sun, 14 Jun 2009 10:55:48 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: Configuration vs. compat hints [was Re: [Qemu-devel] [PATCHv3 03/13] qemu: add routines to manage PCI capabilities] References: <20090610145540.GI19375@poweredge.glommer> <20090610150129.GC28601@redhat.com> <200906101624.30659.paul@codesourcery.com> <20090610174301.GC7416@shareable.org> <20090610182227.GN28601@redhat.com> <20090610192702.GH7416@shareable.org> <1244796209.16425.20.camel@blaa> <4A326B5C.5010501@codemonkey.ws> In-Reply-To: <4A326B5C.5010501@codemonkey.ws> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Carsten Otte , Rusty Russell , kvm@vger.kernel.org, Mark McLoughlin , Glauber Costa , "Michael S. Tsirkin" , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook Anthony Liguori wrote: > > What's the problem with parsing the device config and modifying it? > Is it just complexity? Two-way modification. Management wants to store the configuration in their database and tell the hypervisor what the machine looks like. If qemu also tells management what the machine looks like, we can easily get conflicts. -- error compiling committee.c: too many arguments to function