diff options
author | Daniel P. Berrange <berrange@redhat.com> | 2015-11-25 10:52:29 +0000 |
---|---|---|
committer | Paolo Bonzini <pbonzini@redhat.com> | 2015-11-26 16:47:44 +0100 |
commit | bfc2a1a1f41c2861b20e8318c0541d0823427802 (patch) | |
tree | 9b1c2479c32c1cd3e658ce98d5fb940b39150f89 | |
parent | 2c189a4e12a37b1c7cae2a2643c378c5af8f67fc (diff) | |
download | qemu-bfc2a1a1f41c2861b20e8318c0541d0823427802.tar.gz qemu-bfc2a1a1f41c2861b20e8318c0541d0823427802.tar.bz2 qemu-bfc2a1a1f41c2861b20e8318c0541d0823427802.zip |
exec: remove warning about mempath and hugetlbfs
The gethugepagesize() method in exec.c printed a warning if
the file path for "-mem-path" or "-object memory-backend-file"
was not on a hugetlbfs filesystem. This warning is bogus, because
QEMU functions perfectly well with the path on a regular tmpfs
filesystem. Use of hugetlbfs vs tmpfs is a choice for the management
application or end user to make as best fits their needs. As such it
is inappropriate for QEMU to have an opinion on whether the user's
choice is right or wrong in this case.
Signed-off-by: Daniel P. Berrange <berrange@redhat.com>
Message-Id: <1448448749-1332-3-git-send-email-berrange@redhat.com>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
-rw-r--r-- | exec.c | 3 |
1 files changed, 0 insertions, 3 deletions
@@ -1196,9 +1196,6 @@ static long gethugepagesize(const char *path, Error **errp) return 0; } - if (fs.f_type != HUGETLBFS_MAGIC) - fprintf(stderr, "Warning: path not on HugeTLBFS: %s\n", path); - return fs.f_bsize; } |