From: "Dr. David Alan Gilbert" <dgilbert@redhat.com>
To: Andrea Arcangeli <aarcange@redhat.com>
Cc: "Kirill A. Shutemov" <kirill@shutemov.name>,
kirill.shutemov@linux.intel.com, "Li,
Liang Z" <liang.z.li@intel.com>, Amit Shah <amit.shah@redhat.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
"quintela@redhat.com" <quintela@redhat.com>,
linux-mm@kvack.org
Subject: Re: [Qemu-devel] post-copy is broken?
Date: Mon, 18 Apr 2016 10:40:57 +0100 [thread overview]
Message-ID: <20160418094056.GB2222@work-vm> (raw)
In-Reply-To: <20160415221943.GJ9976@redhat.com>
* Andrea Arcangeli (aarcange@redhat.com) wrote:
> On Fri, Apr 15, 2016 at 06:23:30PM +0300, Kirill A. Shutemov wrote:
> > The same here. Freshly booted machine with 64GiB ram. I've checked
> > /proc/vmstat: huge pages were allocated
>
> I tried the test in a loop and I can't reproduce it here.
>
> Tested with gcc 4.9.3 and glibc 2.21 and glibc 2.22 so far,
> qemu&kernel/KVM latest upstream (4.6-rc3..).
>
> You can run this in between each invocation to guarantee all memory is
> backed by THP (no need of reboot):
>
> # echo 3 >/proc/sys/vm/drop_caches
> # echo >/proc/sys/vm/compact_memory
>
> 4.5 kernel built with gcc 5.3.1 run on a older userland worked fine
> too.
>
> Next thing to test would be if there's something wrong with qemu built
> with gcc 5.3.1 if run on top of a 4.4 kernel?
It's also working for me on f24 (4.5.0-320 packaged kernel) on a real machine;
so we currently have two sets that break:
a) Liang Li's setup (that breaks with the migrate of a real VM but I don't
think we have any details of the setup);
works with 4.4.x breaks with 4.5.x
b) f24 nested with my test, with THP enabled after Kirill's changes.
Dave
--
Dr. David Alan Gilbert / dgilbert@redhat.com / Manchester, UK
next prev parent reply other threads:[~2016-04-18 9:41 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 9:23 [Qemu-devel] post-copy is broken? Li, Liang Z
2016-04-12 9:37 ` Dr. David Alan Gilbert
2016-04-12 17:55 ` Dr. David Alan Gilbert
2016-04-13 0:43 ` Li, Liang Z
2016-04-13 2:28 ` Li, Liang Z
2016-04-13 8:06 ` Dr. David Alan Gilbert
2016-04-13 11:41 ` Dr. David Alan Gilbert
2016-04-13 12:50 ` Dr. David Alan Gilbert
2016-04-13 20:51 ` Andrea Arcangeli
2016-04-14 10:13 ` Dr. David Alan Gilbert
2016-04-14 12:34 ` Dr. David Alan Gilbert
2016-04-14 16:22 ` Andrea Arcangeli
2016-04-15 12:52 ` Kirill A. Shutemov
2016-04-15 13:42 ` Dr. David Alan Gilbert
2016-04-15 15:23 ` Kirill A. Shutemov
2016-04-15 16:34 ` Dr. David Alan Gilbert
2016-04-18 9:50 ` Li, Liang Z
2016-04-18 9:55 ` Dr. David Alan Gilbert
2016-04-18 10:06 ` Li, Liang Z
2016-04-18 10:15 ` Dr. David Alan Gilbert
2016-04-18 10:33 ` Li, Liang Z
2016-04-18 13:23 ` Dr. David Alan Gilbert
2016-04-18 17:18 ` Dr. David Alan Gilbert
2016-04-20 17:27 ` Dr. David Alan Gilbert
2016-04-21 19:21 ` Dr. David Alan Gilbert
2016-04-27 14:47 ` Andrea Arcangeli
2016-04-28 2:59 ` Li, Liang Z
2016-04-28 8:03 ` Dr. David Alan Gilbert
2016-04-15 22:19 ` Andrea Arcangeli
2016-04-18 9:40 ` Dr. David Alan Gilbert [this message]
2016-04-18 9:58 ` Li, Liang Z
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=20160418094056.GB2222@work-vm \
--to=dgilbert@redhat.com \
--cc=aarcange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kirill@shutemov.name \
--cc=liang.z.li@intel.com \
--cc=linux-mm@kvack.org \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).