From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: async pf: INFO: SOFTIRQ-safe -> SOFTIRQ-unsafe lock order detected Date: Sun, 06 May 2012 15:00:23 +0300 Message-ID: <4FA667D7.4040201@redhat.com> References: <20120502120402.GM22191@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: Sasha Levin , Marcelo Tosatti , "linux-kernel@vger.kernel.org List" , kvm@vger.kernel.org, Paul McKenney To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:8034 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753372Ab2EFMA3 (ORCPT ); Sun, 6 May 2012 08:00:29 -0400 In-Reply-To: <20120502120402.GM22191@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: On 05/02/2012 03:04 PM, Gleb Natapov wrote: > KVM: Do not take reference to mm during async #PF > > It turned to be totally unneeded. The reason the code was introduced is > so that KVM can prefault swapped in page, but prefault can fail even > if mm is pinned since page table can change anyway. KVM handles this > situation correctly though and does not inject spurious page faults. > > Applied to master for 3.4, thanks. -- error compiling committee.c: too many arguments to function