From: "Xu, Qian Q" <qian.q.xu@intel.com>
To: Thomas Monjalon <thomas.monjalon@6wind.com>,
Marcel Apfelbaum <marcel@redhat.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>, "Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [dpdk-dev] [PATCH] vhost-user: enable virtio 1.0
Date: Tue, 3 Nov 2015 03:45:04 +0000 [thread overview]
Message-ID: <82F45D86ADE5454A95A89742C8D1410E0317151D@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <2518261.T4ICXTenZs@xps13>
DPDK GCC 64bit build on kernel 3.18 will be failed, could you help check?
== Build lib/librte_pipeline
/home/qxu10/virtio-opt-test/dpdk/lib/librte_vhost/virtio-net.c:81:106: error: 'VIRTIO_F_VERSION_1' undeclared here (not in a function)
static uint64_t VHOST_FEATURES = VHOST_SUPPORTED_FEATURES;
^
/home/qxu10/virtio-opt-test/dpdk/mk/internal/rte.compile-pre.mk:126: recipe for target 'virtio-net.o' failed
make[5]: *** [virtio-net.o] Error 1
/home/qxu10/virtio-opt-test/dpdk/mk/rte.subdir.mk:61: recipe for target 'librte_vhost' failed
make[4]: *** [librte_vhost] Error 2
make[4]: *** Waiting for unfinished jobs....
SYMLINK-FILE include/rte_pipeline.h
CC rte_pipeline.o
AR librte_pipeline.a
INSTALL-LIB librte_pipeline.a
/home/qxu10/virtio-opt-test/dpdk/mk/rte.sdkbuild.mk:93: recipe for target 'lib' failed
make[3]: *** [lib] Error 2
/home/qxu10/virtio-opt-test/dpdk/mk/rte.sdkroot.mk:124: recipe for target 'all' failed
make[2]: *** [all] Error 2
/home/qxu10/virtio-opt-test/dpdk/mk/rte.sdkinstall.mk:58: recipe for target 'x86_64-native-linuxapp-gcc_install' failed
make[1]: *** [x86_64-native-linuxapp-gcc_install] Error 2
/home/qxu10/virtio-opt-test/dpdk/mk/rte.sdkroot.mk:102: recipe for target 'install' failed
make: *** [install] Error 2
Thanks
Qian
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
Sent: Tuesday, November 03, 2015 6:14 AM
To: Marcel Apfelbaum
Cc: dev@dpdk.org; Michael S. Tsirkin
Subject: Re: [dpdk-dev] [PATCH] vhost-user: enable virtio 1.0
> > Make vhost-user virtio 1.0 compatible by adding it to the supported
> > features and keeping the header length the same as for mergeable RX
> > buffers.
> >
> > Signed-off-by: Marcel Apfelbaum <marcel@redhat.com>
>
> Looks good to me
>
> Acked-by: Michael S. Tsirkin <mst@redhat.com>
Applied, thanks
next prev parent reply other threads:[~2015-11-03 3:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-15 11:08 Marcel Apfelbaum
2015-10-15 13:18 ` Michael S. Tsirkin
2015-10-16 2:24 ` Yuanhan Liu
2015-10-16 6:20 ` Michael S. Tsirkin
2015-10-16 7:43 ` Andriy Berestovskyy
2015-10-16 7:50 ` Yuanhan Liu
2015-10-16 7:56 ` Michael S. Tsirkin
2015-10-16 13:52 ` Bruce Richardson
2015-10-18 7:04 ` Michael S. Tsirkin
2015-10-30 17:48 ` Thomas Monjalon
2015-11-01 9:00 ` Marcel Apfelbaum
2015-11-01 9:53 ` Thomas Monjalon
2015-11-01 11:22 ` Marcel Apfelbaum
2015-11-09 19:55 ` Michael S. Tsirkin
2015-11-02 22:13 ` Thomas Monjalon
2015-11-03 3:45 ` Xu, Qian Q [this message]
2015-11-03 3:49 ` Xu, Qian Q
2015-11-03 8:03 ` Marcel Apfelbaum
2015-11-03 8:16 ` Xie, Huawei
2015-11-03 8:26 ` Thomas Monjalon
2015-11-03 8:30 ` Marcel Apfelbaum
2015-11-03 8:31 ` Marcel Apfelbaum
2015-10-16 6:39 ` Yuanhan Liu
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=82F45D86ADE5454A95A89742C8D1410E0317151D@shsmsx102.ccr.corp.intel.com \
--to=qian.q.xu@intel.com \
--cc=dev@dpdk.org \
--cc=marcel@redhat.com \
--cc=mst@redhat.com \
--cc=thomas.monjalon@6wind.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 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).