From: Andrea Arcangeli <aarcange@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
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: post-copy is broken?
Date: Fri, 15 Apr 2016 18:19:43 -0400 [thread overview]
Message-ID: <20160415221943.GJ9976@redhat.com> (raw)
In-Reply-To: <20160415152330.GB3376@node.shutemov.name>
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?
--
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>
WARNING: multiple messages have this Message-ID (diff)
From: Andrea Arcangeli <aarcange@redhat.com>
To: "Kirill A. Shutemov" <kirill@shutemov.name>
Cc: "Dr. David Alan Gilbert" <dgilbert@redhat.com>,
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: Fri, 15 Apr 2016 18:19:43 -0400 [thread overview]
Message-ID: <20160415221943.GJ9976@redhat.com> (raw)
In-Reply-To: <20160415152330.GB3376@node.shutemov.name>
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?
next prev parent reply other threads:[~2016-04-15 22:19 UTC|newest]
Thread overview: 51+ 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-14 16:22 ` [Qemu-devel] " Andrea Arcangeli
2016-04-15 12:52 ` Kirill A. Shutemov
2016-04-15 12:52 ` [Qemu-devel] " Kirill A. Shutemov
2016-04-15 13:42 ` Dr. David Alan Gilbert
2016-04-15 13:42 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-15 15:23 ` Kirill A. Shutemov
2016-04-15 15:23 ` [Qemu-devel] " Kirill A. Shutemov
2016-04-15 16:34 ` Dr. David Alan Gilbert
2016-04-15 16:34 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-18 9:50 ` Li, Liang Z
2016-04-18 9:50 ` [Qemu-devel] " Li, Liang Z
2016-04-18 9:55 ` Dr. David Alan Gilbert
2016-04-18 9:55 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-18 10:06 ` Li, Liang Z
2016-04-18 10:06 ` [Qemu-devel] " Li, Liang Z
2016-04-18 10:15 ` Dr. David Alan Gilbert
2016-04-18 10:15 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-18 10:33 ` Li, Liang Z
2016-04-18 10:33 ` [Qemu-devel] " Li, Liang Z
2016-04-18 13:23 ` Dr. David Alan Gilbert
2016-04-18 13:23 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-18 17:18 ` Dr. David Alan Gilbert
2016-04-18 17:18 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-20 17:27 ` Dr. David Alan Gilbert
2016-04-20 17:27 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-21 19:21 ` Dr. David Alan Gilbert
2016-04-21 19:21 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-27 14:47 ` Andrea Arcangeli
2016-04-27 14:47 ` [Qemu-devel] " Andrea Arcangeli
2016-04-28 2:59 ` Li, Liang Z
2016-04-28 2:59 ` [Qemu-devel] " Li, Liang Z
2016-04-28 8:03 ` Dr. David Alan Gilbert
2016-04-28 8:03 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-15 22:19 ` Andrea Arcangeli [this message]
2016-04-15 22:19 ` Andrea Arcangeli
2016-04-18 9:40 ` Dr. David Alan Gilbert
2016-04-18 9:40 ` [Qemu-devel] " Dr. David Alan Gilbert
2016-04-18 9:58 ` Li, Liang Z
2016-04-18 9:58 ` [Qemu-devel] " 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=20160415221943.GJ9976@redhat.com \
--to=aarcange@redhat.com \
--cc=amit.shah@redhat.com \
--cc=dgilbert@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 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.