From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MF8Aq-0006eE-Ly for qemu-devel@nongnu.org; Fri, 12 Jun 2009 10:56:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MF8Ak-0006W7-0n for qemu-devel@nongnu.org; Fri, 12 Jun 2009 10:56:08 -0400 Received: from [199.232.76.173] (port=48575 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MF8Aj-0006Vv-PT for qemu-devel@nongnu.org; Fri, 12 Jun 2009 10:56:01 -0400 Received: from mail-gx0-f207.google.com ([209.85.217.207]:48295) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MF8Aj-0007t8-KS for qemu-devel@nongnu.org; Fri, 12 Jun 2009 10:56:01 -0400 Received: by gxk3 with SMTP id 3so9472354gxk.10 for ; Fri, 12 Jun 2009 07:56:00 -0700 (PDT) Message-ID: <4A326C7E.3020309@codemonkey.ws> Date: Fri, 12 Jun 2009 09:55:58 -0500 From: Anthony Liguori 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> In-Reply-To: <1244796209.16425.20.camel@blaa> 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: Mark McLoughlin Cc: Carsten Otte , kvm@vger.kernel.org, "Michael S. Tsirkin" , Glauber Costa , Rusty Russell , qemu-devel@nongnu.org, virtualization@lists.linux-foundation.org, Blue Swirl , Christian Borntraeger , Paul Brook , Avi Kivity Mark McLoughlin wrote: > On Wed, 2009-06-10 at 20:27 +0100, Jamie Lokier wrote: > > = Solution - Separate configuration from compat hints = > > As I suggested before: > > - Allow the VM manager to dump compat hints; this would be an opaque > file format, more like the savevm format than a config file > How is compat hints different from a device tree? In my mind, that's what compat hints is. I don't see another sane way to implement it. Regards, Anthony Liguori