From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH V2 5/5] vga-cirrus: Workaround during restore when using Xen. Date: Fri, 06 Jan 2012 14:19:18 +0200 Message-ID: <4F06E6C6.5080607@redhat.com> References: <1323467645-24271-1-git-send-email-anthony.perard@citrix.com> <1323467645-24271-6-git-send-email-anthony.perard@citrix.com> <4EE3382D.80903@web.de> <4EE609BF.1070307@siemens.com> <4EE617BA.4030102@siemens.com> <4EEE25DA.2080400@redhat.com> <4F048B10.1060505@redhat.com> <4F059C8C.2030303@redhat.com> <4F05A684.7000509@redhat.com> <4F05BF9E.7000203@redhat.com> <4F05D0BC.70707@redhat.com> <4F05E301.2020808@redhat.com> <4F05F09E.8030800@web.de> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4F05F09E.8030800@web.de> 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: Jan Kiszka Cc: Anthony Perard , Xen Devel , QEMU-devel , Stefano Stabellini List-Id: xen-devel@lists.xenproject.org On 01/05/2012 08:49 PM, Jan Kiszka wrote: > To me this still sounds like a cirrus-only xen workaround that > nevertheless spreads widely. It is. > Again, what speaks against migrating the information Xen needs before > creating the machine or a single device? That would only introduce a > generic concept of an (optional) "early", let's call it > "accelerator-related" vmstate and would allow Xen to deal with all the > specifics behind the curtain. > Adding more concepts, just to work around a bug (and this is really a bug in the qemu/xen interface) makes it harder to refactor things later on. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.