From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Jan Beulich" Subject: Re: Re: issues with movnti emulation Date: Mon, 24 Nov 2008 15:34:23 +0000 Message-ID: <492AD78F.76E4.0078.0@novell.com> References: <20081120171641.GJ25331@york.uk.xensource.com> <20081121160152.GK25331@york.uk.xensource.com><20081121160152.GK25331@york.uk.xensource.com> <492AD3E4.9060309@eu.citrix.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <492AD3E4.9060309@eu.citrix.com> Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Gianluca Guida Cc: xen-devel@lists.xensource.com, Tim Deegan , Keir Fraser List-Id: xen-devel@lists.xenproject.org >>> Gianluca Guida 24.11.08 17:18 >>> >Tim Deegan wrote: >> At 17:43 +0000 on 20 Nov (1227202988), Keir Fraser wrote: >>> Yes, you're probably right. I wonder if we are relying on emulation = failures >>> to inform unshadowing at all often? We might have to revisit constraini= ng >>> x86_emulate() when called by shadow code, do you think? >>=20 >> Yes, I think it would probably be worth looking at that. > >In what kind of guest/workloads we were experiencing this corruption? SLE11 installation. Jan