From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1M0WSv-0004r5-PQ for qemu-devel@nongnu.org; Sun, 03 May 2009 03:50:25 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1M0WSr-0004qC-9L for qemu-devel@nongnu.org; Sun, 03 May 2009 03:50:25 -0400 Received: from [199.232.76.173] (port=46650 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1M0WSr-0004q7-1I for qemu-devel@nongnu.org; Sun, 03 May 2009 03:50:21 -0400 Received: from mx2.redhat.com ([66.187.237.31]:47943) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1M0WSq-0007Q6-EH for qemu-devel@nongnu.org; Sun, 03 May 2009 03:50:20 -0400 Message-ID: <49FD4CB4.3070008@redhat.com> Date: Sun, 03 May 2009 10:50:12 +0300 From: Avi Kivity MIME-Version: 1.0 Subject: Re: [Qemu-devel] Re: [PATCH 0/8] kvm: Fixes, cleanups and live migration References: <20090501211717.24514.23246.stgit@mchn012c.ww002.siemens.net> <49FB7A40.1020005@us.ibm.com> <20090502074041.GB7198@redhat.com> <49FC4F90.1030901@codemonkey.ws> <20090502172308.GA13933@redhat.com> <49FC9B39.4080408@redhat.com> <20090502200754.GB13933@redhat.com> <49FD3266.5050000@redhat.com> <20090503060502.GH9795@redhat.com> <49FD4996.9060606@redhat.com> <20090503074648.GI9795@redhat.com> In-Reply-To: <20090503074648.GI9795@redhat.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Gleb Natapov Cc: Anthony Liguori , Jan Kiszka , qemu-devel@nongnu.org Gleb Natapov wrote: >> Maybe we should unexecute the software interrupt instruction on Intel >> and get the same effect. >> >> > We don't need to unexecute anything. We get exit with RIP pointing to > the offending instruction. The right thing on VMX to do is to inject > software interrupt with correct instruction length. Processor will do > the rest. Remind me please why do we try to find problems where there is > none? We will do right thing and fix migration code to do right thing. > > I don't want the migration protocol to encode vendor specific information. The architectural state is complicated enough, we don't want microarchitectural state as well. -- error compiling committee.c: too many arguments to function