From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jan Kiszka Subject: Re: [PATCH v2 0/4] Emulate VMXON region correctly Date: Wed, 04 Jun 2014 09:18:36 +0200 Message-ID: <538EC84C.90401@siemens.com> References: <1399357158-8305-1-git-send-email-bsd@redhat.com> <5369156F.1070104@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 7bit Cc: kvm@vger.kernel.org, Gleb Natapov , Marcelo Tosatti , linux-kernel@vger.kernel.org To: Bandan Das , Paolo Bonzini Return-path: Received: from goliath.siemens.de ([192.35.17.28]:44324 "EHLO goliath.siemens.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754956AbaFDHS5 (ORCPT ); Wed, 4 Jun 2014 03:18:57 -0400 In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On 2014-06-03 22:11, Bandan Das wrote: > Paolo Bonzini writes: > >> Il 06/05/2014 08:19, Bandan Das ha scritto: >>> Reference: https://bugzilla.kernel.org/show_bug.cgi?id=54521 >>> >>> The vmxon region is unused by nvmx, but adding these checks >>> are probably harmless and may detect buggy L1 hypervisors in >>> the future! >> >> Applied to kvm/queue, unit test patches are welcome (hint, hint!). > > Jan and Paolo, > > Ok, I thought a little bit about this and I am wondering what > kind of tests we could have here. All the changes are pure > checks and no data is returned back to the guest. The > vmxon code in kvm-unit-tests already does the right thing i.e > sets the revision identifier, allocs a page for the region etc Then try to do the wrong thing in the unit test and validate that you get the right error report from the emulated VMX hardware. Jan -- Siemens AG, Corporate Technology, CT RTC ITP SES-DE Corporate Competence Center Embedded Linux