From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH v4 0/6] save/restore on Xen Date: Tue, 24 Jan 2012 13:13:01 +0200 Message-ID: <4F1E923D.2090208@redhat.com> References: <4F19AB66.8060901@siemens.com> <4F1D4974.4090003@siemens.com> <4F1D4E43.7000501@siemens.com> <4F1D80BA.1040504@siemens.com> <4F1D9546.4040801@siemens.com> <4F1D9649.1000102@codemonkey.ws> <4F1D995A.4020604@siemens.com> <4F1D9A8E.1080102@codemonkey.ws> <4F1E8635.2020608@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F1E8635.2020608@redhat.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org Sender: qemu-devel-bounces+gceq-qemu-devel=gmane.org@nongnu.org To: Gerd Hoffmann Cc: Jan Kiszka , "xen-devel@lists.xensource.com" , "qemu-devel@nongnu.org" , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 01/24/2012 12:21 PM, Gerd Hoffmann wrote: > >>> > >>> But viewing RAM as just another device, having Xen only restore a > >>> subset of > >>> devices should be a reasonable thing to do moving forward. > > I don't think modeling device memory (i.e. vga vram) as something > independent from the device (vga) is a good idea. Because it isn't. Right. We should have VMSTATE_RAM() to express the dependency. -- error compiling committee.c: too many arguments to function