From: liming.wu@jaguarmicro.com
To: "Michael S . Tsirkin" <mst@redhat.com>, Jason Wang <jasowang@redhat.com>
Cc: kvm@vger.kernel.org, virtualization@lists.linux-foundation.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Liming Wu <liming.wu@jaguarmicro.com>
Subject: [PATCH v2 2/2] tools/virtio: Add hints when module is not installed
Date: Sun, 8 Oct 2023 11:17:34 +0800 [thread overview]
Message-ID: <20231008031734.1095-2-liming.wu@jaguarmicro.com> (raw)
In-Reply-To: <20231008031734.1095-1-liming.wu@jaguarmicro.com>
From: Liming Wu <liming.wu@jaguarmicro.com>
Need to insmod vhost_test.ko before run virtio_test.
Give some hints to users.
Signed-off-by: Liming Wu <liming.wu@jaguarmicro.com>
---
tools/virtio/virtio_test.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/tools/virtio/virtio_test.c b/tools/virtio/virtio_test.c
index 028f54e6854a..13572a677c35 100644
--- a/tools/virtio/virtio_test.c
+++ b/tools/virtio/virtio_test.c
@@ -135,6 +135,10 @@ static void vdev_info_init(struct vdev_info* dev, unsigned long long features)
dev->buf = malloc(dev->buf_size);
assert(dev->buf);
dev->control = open("/dev/vhost-test", O_RDWR);
+
+ if (dev->control < 0)
+ fprintf(stderr,
+ "Install vhost_test module (./vhost_test/vhost_test.ko) first.\n");
assert(dev->control >= 0);
r = ioctl(dev->control, VHOST_SET_OWNER, NULL);
assert(r >= 0);
--
2.34.1
next prev parent reply other threads:[~2023-10-08 3:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 3:17 [PATCH v2 1/2] tools/virtio: Add dma sync api for virtio test liming.wu
2023-10-08 3:17 ` liming.wu [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-09-27 15:20 [PATCH 2/2] tools/virtio: Add hints when module is not installed Michael S. Tsirkin
2023-10-07 6:55 ` [PATCH v2 1/2] tools/virtio: Add dma sync api for virtio test liming.wu
2023-10-07 6:55 ` [PATCH v2 2/2] tools/virtio: Add hints when module is not installed liming.wu
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=20231008031734.1095-2-liming.wu@jaguarmicro.com \
--to=liming.wu@jaguarmicro.com \
--cc=jasowang@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=virtualization@lists.linux-foundation.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
all inboxes | Powered by JetHome®