From: marcandre.lureau@redhat.com
To: qemu-devel@nongnu.org
Cc: pbonzini@redhat.com, "Marc-André Lureau" <marcandre.lureau@redhat.com>
Subject: [Qemu-devel] [PATCH 9/9] tests: use memfd in vhost-user-test
Date: Tue, 12 Apr 2016 13:55:29 +0200 [thread overview]
Message-ID: <1460462129-17363-10-git-send-email-marcandre.lureau@redhat.com> (raw)
In-Reply-To: <1460462129-17363-1-git-send-email-marcandre.lureau@redhat.com>
From: Marc-André Lureau <marcandre.lureau@redhat.com>
This will exercise the memfd memory backend and should generally be
better for testing than memory-backend-file (thanks to anonymous files
and sealing).
Signed-off-by: Marc-André Lureau <marcandre.lureau@redhat.com>
---
tests/vhost-user-test.c | 12 ++++++------
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/tests/vhost-user-test.c b/tests/vhost-user-test.c
index 6961596..6ef6c48 100644
--- a/tests/vhost-user-test.c
+++ b/tests/vhost-user-test.c
@@ -32,8 +32,8 @@
#endif
#define QEMU_CMD_ACCEL " -machine accel=tcg"
-#define QEMU_CMD_MEM " -m %d -object memory-backend-file,id=mem,size=%dM,"\
- "mem-path=%s,share=on -numa node,memdev=mem"
+#define QEMU_CMD_MEM " -m %d -object memory-backend-memfd,id=mem,size=%dM"\
+ " -numa node,memdev=mem"
#define QEMU_CMD_CHR " -chardev socket,id=%s,path=%s"
#define QEMU_CMD_NETDEV " -netdev vhost-user,id=net0,chardev=%s,vhostforce"
#define QEMU_CMD_NET " -device virtio-net-pci,netdev=net0,romfile=./pc-bios/pxe-virtio.rom"
@@ -383,12 +383,12 @@ static TestServer *test_server_new(const gchar *name)
return server;
}
-#define GET_QEMU_CMD(s) \
- g_strdup_printf(QEMU_CMD, 512, 512, (root), (s)->chr_name, \
+#define GET_QEMU_CMD(s) \
+ g_strdup_printf(QEMU_CMD, 512, 512, (s)->chr_name, \
(s)->socket_path, (s)->chr_name)
-#define GET_QEMU_CMDE(s, mem, extra, ...) \
- g_strdup_printf(QEMU_CMD extra, (mem), (mem), (root), (s)->chr_name, \
+#define GET_QEMU_CMDE(s, mem, extra, ...) \
+ g_strdup_printf(QEMU_CMD extra, (mem), (mem), (s)->chr_name, \
(s)->socket_path, (s)->chr_name, ##__VA_ARGS__)
static gboolean _test_server_free(TestServer *server)
--
2.5.5
prev parent reply other threads:[~2016-04-12 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-12 11:55 [Qemu-devel] [PATCH 0/9] RFC: add memfd memory backend marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 1/9] exec: check kvm mmu notifiers earlier marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 2/9] exec: split file_ram_alloc() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 3/9] exec: split qemu_ram_alloc_from_file() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 4/9] Add memory_region_init_ram_from_fd() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 5/9] RFC: ivshmem: use ram_from_fd() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 6/9] exec: remove qemu_set_ram_fd() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 7/9] memfd: split qemu_memfd_alloc() marcandre.lureau
2016-04-12 11:55 ` [Qemu-devel] [PATCH 8/9] Add memfd based hostmem marcandre.lureau
2016-04-12 13:07 ` Igor Mammedov
2016-04-12 13:32 ` Marc-André Lureau
2016-04-12 11:55 ` marcandre.lureau [this message]
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=1460462129-17363-10-git-send-email-marcandre.lureau@redhat.com \
--to=marcandre.lureau@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
/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).