From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756014Ab2ISAOU (ORCPT ); Tue, 18 Sep 2012 20:14:20 -0400 Received: from mail.linuxfoundation.org ([140.211.169.12]:39577 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752628Ab2ISAOQ (ORCPT ); Tue, 18 Sep 2012 20:14:16 -0400 Date: Tue, 18 Sep 2012 17:20:29 -0700 From: Andrew Morton To: Stephen Rothwell Cc: Jiri Slaby , Avi Kivity , Jiri Slaby , Marcelo Tosatti , kvm@vger.kernel.org, LKML , Haggai Eran , linux-mm@kvack.org, Sagi Grimberg , Shachar Raindel , Liran Liss Subject: Re: qemu-kvm loops after kernel udpate Message-Id: <20120918172029.b5425a40.akpm@linux-foundation.org> In-Reply-To: <20120919100034.ceaee306e24e00cdf6f1e92e@canb.auug.org.au> References: <504F7ED8.1030702@suse.cz> <20120911190303.GA3626@amt.cnet> <504F93F1.2060005@suse.cz> <50504299.2050205@redhat.com> <50504439.3050700@suse.cz> <5050453B.6040702@redhat.com> <5050D048.4010704@suse.cz> <5051AE8B.7090904@redhat.com> <5058CE2F.7030302@suse.cz> <20120918124646.02aaee4f.akpm@linux-foundation.org> <20120919100034.ceaee306e24e00cdf6f1e92e@canb.auug.org.au> X-Mailer: Sylpheed 2.7.1 (GTK+ 2.18.9; x86_64-redhat-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, 19 Sep 2012 10:00:34 +1000 Stephen Rothwell wrote: > Hi Andrew, > > On Tue, 18 Sep 2012 12:46:46 -0700 Andrew Morton wrote: > > > > hm, thanks. This will probably take some time to resolve so I think > > I'll drop > > > > mm-move-all-mmu-notifier-invocations-to-be-done-outside-the-pt-lock.patch > > mm-move-all-mmu-notifier-invocations-to-be-done-outside-the-pt-lock-fix.patch > > mm-move-all-mmu-notifier-invocations-to-be-done-outside-the-pt-lock-fix-fix.patch > > mm-wrap-calls-to-set_pte_at_notify-with-invalidate_range_start-and-invalidate_range_end.patch > > Should I attempt to remove these from the akpm tree in linux-next today? That would be best - there's no point in having people test (and debug) dead stuff. > Or should I just wait for a new mmotm? You could be brave and test http://ozlabs.org/~akpm/mmots/ for me :)