From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mns3Y-0004HI-36 for qemu-devel@nongnu.org; Wed, 16 Sep 2009 06:48:12 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mns3T-0004FS-TD for qemu-devel@nongnu.org; Wed, 16 Sep 2009 06:48:11 -0400 Received: from [199.232.76.173] (port=48237 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mns3T-0004FI-Kv for qemu-devel@nongnu.org; Wed, 16 Sep 2009 06:48:07 -0400 Received: from mx1.redhat.com ([209.132.183.28]:29482) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mns3S-0008EB-E3 for qemu-devel@nongnu.org; Wed, 16 Sep 2009 06:48:06 -0400 Received: from int-mx04.intmail.prod.int.phx2.redhat.com (int-mx04.intmail.prod.int.phx2.redhat.com [10.5.11.17]) by mx1.redhat.com (8.13.8/8.13.8) with ESMTP id n8GAm52R024187 for ; Wed, 16 Sep 2009 06:48:05 -0400 Date: Wed, 16 Sep 2009 13:46:20 +0300 From: "Michael S. Tsirkin" Message-ID: <20090916104620.GA4456@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Subject: [Qemu-devel] optional feature (was Re: The State of the SaveVM format) List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Juan Quintela , gleb@redhat.com Cc: qemu-devel@nongnu.org On Wed, Sep 09, 2009 at 10:47:27AM +0200, Juan Quintela wrote: > How do we deal with optional features? Here's an idea that Gleb suggested in a private conversation: make optional features into separate, non-user-visible devices. Thus we would have vmstate for virtio and additionally, if msix is enabled, vmstate for msix. This solves the problem of the number of devices becoming exponential with the number of features: we have device per feature. I understand that RTC does something like this. Happy? -- MST