From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: kernel bug in kvm_intel Date: Sun, 01 Nov 2009 11:00:31 +0100 Message-ID: <4AED5C3F.9050506@kernel.org> References: <4ACF9745.3050902@linux.vnet.ibm.com> <4AD16ACE.6040903@redhat.com> <1255372957.4883.49.camel@twinturbo.austin.ibm.com> <4AD4231F.6040608@redhat.com> <1255442640.4883.56.camel@twinturbo.austin.ibm.com> <4AD6061D.5070306@redhat.com> <1255637909.4883.129.camel@twinturbo.austin.ibm.com> <1256926052.4883.203.camel@twinturbo.austin.ibm.com> <4AEC5C24.9080506@redhat.com> <4AEC64FC.7070908@linux.vnet.ibm.com> <4AEC6699.6000202@redhat.com> <4AEC6821.7010801@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Cc: Andrew Theurer , kvm@vger.kernel.org To: Avi Kivity Return-path: Received: from hera.kernel.org ([140.211.167.34]:35653 "EHLO hera.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751079AbZKAJ7l (ORCPT ); Sun, 1 Nov 2009 04:59:41 -0500 In-Reply-To: <4AEC6821.7010801@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: Hello, Avi Kivity wrote: > Only, that merge doesn't change virt/kvm or arch/x86/kvm. > > Tejun, anything known bad about that merge? ada3fa15 kills kvm. Nothing rings a bell at the moment. How does it kill kvm? One big difference caused by that merge is use of sparse areas near the top of vmalloc area. This caused vmalloc area shortage on sparc64 and exposed paging code bug on ppc64 which caused the cpu to fault repeatedly on the same address. Maybe something similiar is happening with kvm? Thanks. -- tejun