From: sys_stv@intel.com
To: test-report@dpdk.org
Cc: maxime.coquelin@redhat.com
Subject: [dpdk-test-report] |FAILURE| pw33192 [PATCH v2] bus/pci: forbid VA as IOVA mode if IOMMU address width too small
Date: 15 Jan 2018 01:56:22 -0800 [thread overview]
Message-ID: <a797f1$l5u1b@fmsmga001.fm.intel.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 5936 bytes --]
Test-Label: Intel-compilation
Test-Status: FAILURE
http://dpdk.org/patch/33192
_Compilation issues_
Submitter: Maxime Coquelin <maxime.coquelin@redhat.com>
Date: Tue, 9 Jan 2018 14:18:01 +0100
DPDK git baseline: Repo:dpdk, Branch:master, CommitID:f477a4696572201cf26534c83a42ec7dc8098fd8
Patch33192-33192 --> compile error
Build Summary: 15 Builds Done, 12 Successful, 3 Failures
Test environment and configuration as below:
OS: FreeBSD10.3_64
Kernel Version:10.3-RELEASE
CPU info: Intel(R) Xeon(R) CPU E5-2699 v4 @ 2.20GHz (2194.97-MHz K8-class CPU)
GCC Version:gcc (FreeBSD Ports Collection) 4.8.5
Clang Version:3.4.1
x86_64-native-bsdapp-clang
x86_64-native-bsdapp-gcc
OS: FC24_64
Kernel Version:4.9.13-100.fc24.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 6.2.1 20160916 (Red Hat 6.2.1-2)
Clang Version:3.8.0
x86_64-native-linuxapp-clang
i686-native-linuxapp-gcc
x86_64-native-linuxapp-gcc
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc-debug
OS: UB1604_64
Kernel Version:4.4.0-81-generic
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (Ubuntu 5.4.0-6ubuntu1~16.04.4) 5.4.0 20160609
Clang Version:3.8.0
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
OS: CentOS7_64
Kernel Version:3.10.0-514.10.2.el7.x86_64
CPU info:Intel(R) Xeon(R) CPU E5-2699 v3 @ 2.30GHz
GCC Version:gcc (GCC) 4.8.5 20150623 (Red Hat 4.8.5-4)
Clang Version:3.4.2
i686-native-linuxapp-gcc
x86_64-native-linuxapp-clang
x86_64-native-linuxapp-gcc-shared
x86_64-native-linuxapp-gcc
Failed Build #1:
OS: FC24_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bus_pci.h/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c: In function ‘pci_one_device_iommu_support_va’:
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:579:20: error: format ‘%lx’ expects argument of type ‘long unsigned int *’, but argument 3 has type ‘uint64_t * {aka long long unsigned int *}’ [-Werror=format=]
if (fscanf(fp, "%lx", &vtd_cap_reg) != 1) {
^
In file included from /home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:8:0:
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:601:10: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=]
sagaw);
^
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:287:25: note: in definition of macro ‘RTE_LOG’
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'linux/pci.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'pci' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'bus' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #2:
OS: UB1604_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bus_pci.h/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c: In function ‘pci_one_device_iommu_support_va’:
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:579:17: error: format ‘%lx’ expects argument of type ‘long unsigned int *’, but argument 3 has type ‘uint64_t * {aka long long unsigned int *}’ [-Werror=format=]
if (fscanf(fp, "%lx", &vtd_cap_reg) != 1) {
^
In file included from /home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:8:0:
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:601:10: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t {aka long long unsigned int}’ [-Werror=format=]
sagaw);
^
/home/patchWorkOrg/compilation/i686-native-linuxapp-gcc/include/rte_log.h:287:25: note: in definition of macro ‘RTE_LOG’
RTE_LOGTYPE_ ## t, # t ": " __VA_ARGS__)
^
cc1: all warnings being treated as errors
/home/patchWorkOrg/compilation/mk/internal/rte.compile-pre.mk:110: recipe for target 'linux/pci.o' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'pci' failed
/home/patchWorkOrg/compilation/mk/rte.subdir.mk:35: recipe for target 'bus' failed
/home/patchWorkOrg/compilation/mk/rte.sdkbuild.mk:48: recipe for target 'drivers' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:100: recipe for target 'all' failed
/home/patchWorkOrg/compilation/mk/rte.sdkinstall.mk:85: recipe for target 'pre_install' failed
/home/patchWorkOrg/compilation/mk/rte.sdkroot.mk:79: recipe for target 'install' failed
Failed Build #3:
OS: CentOS7_64
Target: i686-native-linuxapp-gcc
SYMLINK-FILE include/rte_bus_pci.h/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c: In function ‘pci_one_device_iommu_support_va’:
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:579:2: error: format ‘%lx’ expects argument of type ‘long unsigned int *’, but argument 3 has type ‘uint64_t *’ [-Werror=format=]
if (fscanf(fp, "%lx", &vtd_cap_reg) != 1) {
^
/home/patchWorkOrg/compilation/drivers/bus/pci/linux/pci.c:600:3: error: format ‘%lx’ expects argument of type ‘long unsigned int’, but argument 4 has type ‘uint64_t’ [-Werror=format=]
RTE_LOG(ERR, EAL, "Unkwown Intel IOMMU SAGAW value (%lx)\n",
^
cc1: all warnings being treated as errors
DPDK STV team
reply other threads:[~2018-01-15 9:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='a797f1$l5u1b@fmsmga001.fm.intel.com' \
--to=sys_stv@intel.com \
--cc=maxime.coquelin@redhat.com \
--cc=test-report@dpdk.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).