From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: [PATCH 10/11] VMX: work around lacking VNMI support Date: Sat, 27 Sep 2008 13:57:56 +0300 Message-ID: <48DE11B4.5060101@redhat.com> References: <48D74CE6.5060008@siemens.com> <48D7504B.7050102@siemens.com> <48DB5CC3.5010104@siemens.com> <48DB688B.6020307@redhat.com> <48DB9EAD.2070709@siemens.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit Cc: "Yang, Sheng" , Gleb Natapov , kvm-devel To: Jan Kiszka Return-path: Received: from mx2.redhat.com ([66.187.237.31]:56124 "EHLO mx2.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752288AbYI0K56 (ORCPT ); Sat, 27 Sep 2008 06:57:58 -0400 In-Reply-To: <48DB9EAD.2070709@siemens.com> Sender: kvm-owner@vger.kernel.org List-ID: Jan Kiszka wrote: > As a workaround (or safety bag), is it imaginable to delay or deny VCPU > snapshots at not yet fully restorable points (like > GUEST_INTERRUPTIBILITY_INFO != 0)? Or stick-your-head-into-the-sand for now? > > Head in sand. The points where we have interrupt shadows should be extremely rare, and the points where it matters even rarer. -- I have a truly marvellous patch that fixes the bug which this signature is too narrow to contain.