From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Slaby <jslaby@suse.cz>, Avi Kivity <avi@redhat.com>,
Jiri Slaby <jirislaby@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Haggai Eran <haggaie@mellanox.com>,
linux-mm@kvack.org, Sagi Grimberg <sagig@mellanox.com>,
Shachar Raindel <raindel@mellanox.com>,
Liran Liss <liranl@mellanox.com>
Subject: Re: qemu-kvm loops after kernel udpate
Date: Tue, 18 Sep 2012 17:20:29 -0700 [thread overview]
Message-ID: <20120918172029.b5425a40.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120919100034.ceaee306e24e00cdf6f1e92e@canb.auug.org.au>
On Wed, 19 Sep 2012 10:00:34 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Tue, 18 Sep 2012 12:46:46 -0700 Andrew Morton <akpm@linux-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 :)
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Jiri Slaby <jslaby@suse.cz>, Avi Kivity <avi@redhat.com>,
Jiri Slaby <jirislaby@gmail.com>,
Marcelo Tosatti <mtosatti@redhat.com>,
kvm@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
Haggai Eran <haggaie@mellanox.com>,
linux-mm@kvack.org, Sagi Grimberg <sagig@mellanox.com>,
Shachar Raindel <raindel@mellanox.com>,
Liran Liss <liranl@mellanox.com>
Subject: Re: qemu-kvm loops after kernel udpate
Date: Tue, 18 Sep 2012 17:20:29 -0700 [thread overview]
Message-ID: <20120918172029.b5425a40.akpm@linux-foundation.org> (raw)
In-Reply-To: <20120919100034.ceaee306e24e00cdf6f1e92e@canb.auug.org.au>
On Wed, 19 Sep 2012 10:00:34 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Andrew,
>
> On Tue, 18 Sep 2012 12:46:46 -0700 Andrew Morton <akpm@linux-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, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-09-19 0:14 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-11 18:11 qemu-kvm loops after kernel udpate Jiri Slaby
2012-09-11 19:03 ` Marcelo Tosatti
2012-09-11 19:41 ` Jiri Slaby
2012-09-12 8:06 ` Avi Kivity
2012-09-12 8:13 ` Jiri Slaby
2012-09-12 8:18 ` Avi Kivity
2012-09-12 8:20 ` Jiri Slaby
2012-09-12 18:11 ` Jiri Slaby
2012-09-13 9:59 ` Avi Kivity
2012-09-13 18:32 ` Jiri Slaby
2012-09-18 19:40 ` Jiri Slaby
2012-09-18 19:40 ` Jiri Slaby
2012-09-18 19:46 ` Andrew Morton
2012-09-18 19:46 ` Andrew Morton
2012-09-19 0:00 ` Stephen Rothwell
2012-09-19 0:20 ` Andrew Morton [this message]
2012-09-19 0:20 ` Andrew Morton
2012-09-19 1:36 ` Stephen Rothwell
2012-09-19 14:18 ` [PATCH] mm: call invalidate_range_end in do_wp_page even for zero pages Haggai Eran
2012-09-19 14:18 ` Haggai Eran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120918172029.b5425a40.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=avi@redhat.com \
--cc=haggaie@mellanox.com \
--cc=jirislaby@gmail.com \
--cc=jslaby@suse.cz \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liranl@mellanox.com \
--cc=mtosatti@redhat.com \
--cc=raindel@mellanox.com \
--cc=sagig@mellanox.com \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.