[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120918172029.b5425a40.akpm@linux-foundation.org>
Date: Tue, 18 Sep 2012 17:20:29 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: Stephen Rothwell <sfr@...b.auug.org.au>
Cc: Jiri Slaby <jslaby@...e.cz>, Avi Kivity <avi@...hat.com>,
Jiri Slaby <jirislaby@...il.com>,
Marcelo Tosatti <mtosatti@...hat.com>, kvm@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>,
Haggai Eran <haggaie@...lanox.com>, linux-mm@...ck.org,
Sagi Grimberg <sagig@...lanox.com>,
Shachar Raindel <raindel@...lanox.com>,
Liran Liss <liranl@...lanox.com>
Subject: Re: qemu-kvm loops after kernel udpate
On Wed, 19 Sep 2012 10:00:34 +1000 Stephen Rothwell <sfr@...b.auug.org.au> wrote:
> Hi Andrew,
>
> On Tue, 18 Sep 2012 12:46:46 -0700 Andrew Morton <akpm@...ux-foundation.org> 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 :)
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists