From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH] KVM: nSVM/nVMX: Implement vmexit on INIT assertion Date: Wed, 27 Feb 2013 12:23:27 +0100 Message-ID: <512DECAF.7020600@siemens.com> References: <512A1EF5.2070709@web.de> <20130225080024.GA411@fermat.math.technion.ac.il> <512B2932.5060909@web.de> <20130227112052.GG26252@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: "Nadav Har'El" , Marcelo Tosatti , Gleb Natapov , "Nakajima, Jun" , kvm To: Joerg Roedel Return-path: Received: from thoth.sbs.de ([192.35.17.2]:23811 "EHLO thoth.sbs.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757904Ab3B0LXh (ORCPT ); Wed, 27 Feb 2013 06:23:37 -0500 In-Reply-To: <20130227112052.GG26252@8bytes.org> Sender: kvm-owner@vger.kernel.org List-ID: On 2013-02-27 12:20, Joerg Roedel wrote: > On Mon, Feb 25, 2013 at 10:04:50AM +0100, Jan Kiszka wrote: >> Is the nested-related state already saved on AMD, J=F6rg? If not, ad= ding >> this one would not make things worse at least. Still, missing user s= pace >> save/restore already breaks reset, not only migration (dunno if this= is >> better on AMD). >=20 > Not sure if this is what you are asking for, but nested state is at n= ot > saved/restored for migration or anything. This is a long-standing iss= ue > which needs to be fixed at some point. As I suspected. That needs to be solved at some point, but for now it would not cause any regression to add another unsaved nested-related state (here: "INIT asserted"). That was my questions. Thanks, Jan --=20 Siemens AG, Corporate Technology, CT RTC ITP SDP-DE Corporate Competence Center Embedded Linux