All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Wolf <kwolf@redhat.com>
To: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>
Cc: snabb-devel@googlegroups.com, mst@redhat.com,
	qemu-devel@nongnu.org, luke@snabb.co,
	a.motakis@virtualopensystems.com, tech@virtualopensystems.com
Subject: Re: [Qemu-devel] [PATCH v10 18/18] Add qtest for vhost-user
Date: Wed, 9 Jul 2014 16:24:03 +0200	[thread overview]
Message-ID: <20140709142403.GG4537@noname.redhat.com> (raw)
In-Reply-To: <20140527120718.15172.9772.stgit@3820>

Am 27.05.2014 um 14:07 hat Nikolay Nikolaev geschrieben:
> This test creates a 'server' chardev to listen for vhost-user messages.
> Once VHOST_USER_SET_MEM_TABLE is received it mmaps each received region,
> and read 1k bytes from it. The read data is compared to data from readl.
> 
> The test requires hugetlbfs to be already mounted and writable. The mount
> point defaults to '/hugetlbfs' and can be specified via the environment
> variable QTEST_HUGETLBFS_PATH.
> 
> The rom pc-bios/pxe-virtio.rom is used to instantiate a virtio pcicontroller.
> 
> Signed-off-by: Antonios Motakis <a.motakis@virtualopensystems.com>
> Signed-off-by: Nikolay Nikolaev <n.nikolaev@virtualopensystems.com>

This breaks the test case build on RHEL 6 because G_TIME_SPAN_SECOND
apparently doesn't exist before glib 2.26.

Kevin

  parent reply	other threads:[~2014-07-09 14:24 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140527120050.15172.94908.stgit@3820>
2014-06-04 19:30 ` [Qemu-devel] [PATCH v10 00/18] Vhost and vhost-net support for userspace based backends Michael S. Tsirkin
2014-06-04 20:03   ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev
     [not found] ` <20140527120330.15172.91211.stgit@3820>
2014-06-05 14:00   ` [Qemu-devel] [PATCH v10 01/18] Add kvm_eventfds_enabled function Paolo Bonzini
     [not found] ` <20140527120638.15172.80806.stgit@3820>
2014-06-05 14:37   ` [Qemu-devel] [PATCH v10 15/18] Add the vhost-user netdev backend to the command line Luiz Capitulino
2014-06-09 13:28     ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev
2014-06-09 13:31       ` Michael S. Tsirkin
2014-06-09 13:43         ` Nikolay Nikolaev
2014-06-05 16:08   ` [Qemu-devel] " Eric Blake
2014-06-09 21:19     ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev
2014-06-09 22:22       ` Eric Blake
     [not found] ` <20140527120651.15172.72895.stgit@3820>
2014-06-05 16:17   ` [Qemu-devel] [PATCH v10 16/18] Add vhost-user protocol documentation Eric Blake
2014-06-08 15:05     ` Michael S. Tsirkin
2014-06-08 15:12 ` [Qemu-devel] [PATCH v10 00/18] Vhost and vhost-net support for userspace based backends Michael S. Tsirkin
2014-06-09 10:14   ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev
     [not found] ` <20140527120718.15172.9772.stgit@3820>
2014-07-09 14:24   ` Kevin Wolf [this message]
2014-07-09 15:09     ` [Qemu-devel] [snabb-devel] Re: [PATCH v10 18/18] Add qtest for vhost-user Nikolay Nikolaev
2014-07-11 18:35     ` [Qemu-devel] " Michael S. Tsirkin
2014-07-11 18:35       ` [Qemu-devel] [snabb-devel] " Nikolay Nikolaev

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=20140709142403.GG4537@noname.redhat.com \
    --to=kwolf@redhat.com \
    --cc=a.motakis@virtualopensystems.com \
    --cc=luke@snabb.co \
    --cc=mst@redhat.com \
    --cc=n.nikolaev@virtualopensystems.com \
    --cc=qemu-devel@nongnu.org \
    --cc=snabb-devel@googlegroups.com \
    --cc=tech@virtualopensystems.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.