From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gleb Natapov Subject: Re: How to recreate MOV-SS blocking vmentry fail Date: Wed, 11 Sep 2013 16:44:09 +0300 Message-ID: <20130911134409.GF17294@redhat.com> References: <20130911125345.GB17294@redhat.com> <52306993.2030907@redhat.com> <20130911130307.GD17294@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Paolo Bonzini , kvm , Jan Kiszka To: Arthur Chunqi Li Return-path: Received: from mx1.redhat.com ([209.132.183.28]:22463 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752788Ab3IKNoM (ORCPT ); Wed, 11 Sep 2013 09:44:12 -0400 Content-Disposition: inline In-Reply-To: Sender: kvm-owner@vger.kernel.org List-ID: On Wed, Sep 11, 2013 at 09:04:26PM +0800, Arthur Chunqi Li wrote: > On Wed, Sep 11, 2013 at 9:03 PM, Gleb Natapov wrote: > > On Wed, Sep 11, 2013 at 03:01:07PM +0200, Paolo Bonzini wrote: > >> Il 11/09/2013 14:53, Gleb Natapov ha scritto: > >> >> > I was trying to recreate MOV-SS blocking vmentry fail (Intel SDM 26.1, > >> >> > 5. a). Here the manual refers to Table 24-3, but later in 26.3.1.5 > >> >> > also describe it. I got confused how this scenario can be recreated. > >> >> > Do you have any ideas? > >> >> > > >> > mov $0, %ss > >> > vmlaunch > >> > >> Probably better to save %ss somewhere around these instructions... :) > >> > > Details, details :) It can be: > > mov %ss, tmp > > mov tmp, $ss > > vmlaunch > Well, this seems hard to test this in our framework ;( vmlaunch is > surrounded with many instructions and we cannot add vmlaunch in exit > handler. > Well, we can put moves always there, or write special test for it, but it is nice to have test, but not very important. -- Gleb.