From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MvwX7-0000lA-LZ for qemu-devel@nongnu.org; Thu, 08 Oct 2009 13:12:05 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MvwX3-0000eZ-TT for qemu-devel@nongnu.org; Thu, 08 Oct 2009 13:12:05 -0400 Received: from [199.232.76.173] (port=40350 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MvwX3-0000eD-JD for qemu-devel@nongnu.org; Thu, 08 Oct 2009 13:12:01 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41556) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MvwX2-000641-Tk for qemu-devel@nongnu.org; Thu, 08 Oct 2009 13:12:01 -0400 Date: Thu, 8 Oct 2009 19:11:57 +0200 From: Gleb Natapov Subject: Re: [Qemu-devel] Re: [PATCH v2 3/9] provide in-kernel ioapic Message-ID: <20091008171157.GE19692@redhat.com> References: <1254953315-5761-3-git-send-email-glommer@redhat.com> <1254953315-5761-4-git-send-email-glommer@redhat.com> <4ACDEDEC.60706@us.ibm.com> <4ACDEF03.6010406@redhat.com> <20091008160726.GD29691@shareable.org> <4ACE10B5.3080509@redhat.com> <20091008162248.GK16702@redhat.com> <4ACE1381.3020804@redhat.com> <20091008163431.GM16702@redhat.com> <4ACE165F.3000506@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4ACE165F.3000506@redhat.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Avi Kivity Cc: Anthony Liguori , Glauber Costa , kvm-devel , qemu-devel@nongnu.org On Thu, Oct 08, 2009 at 06:42:07PM +0200, Avi Kivity wrote: > On 10/08/2009 06:34 PM, Gleb Natapov wrote: > >So suppose I have simple watchdog device that required to be poked every > >second, otherwise it resets a computer. On migration we have to migrate > >time elapsed since last poke, but if device doesn't expose it to > >software in any way you are saying we can recreate is some other way? > > The time is exposed (you can measure it by poking the device and The time yes, not its internal representation. What if one implementation stores how much time passed and another how much time left. One counts in wall clack another only when guest runs. etc... and this is a device with only one write only register. > measuring the time till reset) and will be described in the spec > (otherwise users will be surprised when their machine resets). > > You don't have to migrate all exposed state, just exposed state that > the guest may rely on. -- Gleb.