From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Tokarev Subject: Re: 2.6.16 Guest Hangs on Boot Date: Thu, 16 Sep 2010 15:35:17 +0400 Message-ID: <4C9200F5.8000607@msgid.tls.msk.ru> References: <1284569606.7482.118.camel@nami.8liens.com> <3C88BDE6-33EF-4056-89DE-8CC9084D407C@suse.de> <1284572907.7482.125.camel@nami.8liens.com> <1D3EBE1C-855B-4481-B352-E86EE730A0ED@suse.de> <1284574022.7482.137.camel@nami.8liens.com> <1284602138.7482.157.camel@nami.8liens.com> <4C91F111.9010508@suse.de> <20100916110247.GA15338@8bytes.org> <1284635477.7482.223.camel@nami.8liens.com> <20100916113255.GB15338@8bytes.org> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: QUOTED-PRINTABLE Cc: Alec Joseph Rivera , Alexander Graf , kvm@vger.kernel.org, Meric Mara , Renan Mara To: Joerg Roedel Return-path: Received: from isrv.corpit.ru ([86.62.121.231]:39144 "EHLO isrv.corpit.ru" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752257Ab0IPLfT (ORCPT ); Thu, 16 Sep 2010 07:35:19 -0400 In-Reply-To: <20100916113255.GB15338@8bytes.org> Sender: kvm-owner@vger.kernel.org List-ID: 16.09.2010 15:32, Joerg Roedel =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > On Thu, Sep 16, 2010 at 07:11:17PM +0800, Alec Joseph Rivera wrote: >> On Thu, 2010-09-16 at 13:02 +0200, Joerg Roedel wrote: >> >> Will wait for a 2.6.36 kernel then or compile a .36-rc myself on fre= e >> time :-) >> >> Thanks, will update the list when either comes. >=20 > Just checked, 2.6.36-rc4 contains the fix for the cmpxchg8b problem o= n > 32 bit hosts. What commit it is? I swear I saw it in 2.6.32-stable somewhere. Is it this one (2.6.32.12= ): =46rom: Gleb Natapov Date: Fri, 19 Mar 2010 15:47:31 +0100 Subject: KVM: x86 emulator: fix memory access during x86 emulation To: stable@kernel.org Cc: Marcelo Tosatti , Avi Kivity ,= Gleb Natapov Message-ID: <1269010059-25309-4-git-send-email-stefan.bader@canonical.c= om> =46rom: Gleb Natapov commit 1871c6020d7308afb99127bba51f04548e7ca84e upstream Currently when x86 emulator needs to access memory, page walk is done w= ith broadest permission possible, so if emulated instruction was executed by userspace process it can still access kernel memory. Fix that by providing correct memory access to page walker during emulation. /mjt