From mboxrd@z Thu Jan 1 00:00:00 1970 From: Marcelo Tosatti Subject: Re: [PATCH 4/4] KVM: Rework of guest debug state writing Date: Wed, 3 Feb 2010 21:49:29 -0200 Message-ID: <20100203234929.GA11012@amt.cnet> References: <372238c800e0d57815f472502fdf78e53463bbb6.1265232579.git.jan.kiszka@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Anthony Liguori , qemu-devel@nongnu.org, Avi Kivity , kvm@vger.kernel.org To: Jan Kiszka Return-path: Received: from mx1.redhat.com ([209.132.183.28]:49772 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757659Ab0BCXuY (ORCPT ); Wed, 3 Feb 2010 18:50:24 -0500 Content-Disposition: inline In-Reply-To: <372238c800e0d57815f472502fdf78e53463bbb6.1265232579.git.jan.kiszka@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Feb 03, 2010 at 10:29:45PM +0100, Jan Kiszka wrote: > So far we synchronized any dirty VCPU state back into the kernel before > updating the guest debug state. This was a tribute to a deficit in x86 > kernels before 2.6.33. But as this is an arch-dependent issue, it is > better handle in the x86 part of KVM and remove the writeback point for > generic code. Jan, This patch breaks migration.