[yocto] [meta-realtime][PATCH] schedtool-dl: Fix SCHED_DEADLINE value out of range

2017-06-29 Thread zhe.he
From: He Zhe 

The upstream commit 3ffb479929c31cbae09de08f94f58b8f0f061d91
tries to fix this issue but it's not complete.

This patch adds flags at the last necessary place.

Signed-off-by: He Zhe 
---
 recipes-tools/schedtool-dl/schedtool-dl.bb |  6 ++-
 ...-add-flags-to-parameters-of-sched_setattr.patch | 56 ++
 2 files changed, 61 insertions(+), 1 deletion(-)
 create mode 100644 
recipes-tools/schedtool-dl/schedtool-dl/0001-schedtool-dl-add-flags-to-parameters-of-sched_setattr.patch

diff --git a/recipes-tools/schedtool-dl/schedtool-dl.bb 
b/recipes-tools/schedtool-dl/schedtool-dl.bb
index 578e5df..20c8919 100644
--- a/recipes-tools/schedtool-dl/schedtool-dl.bb
+++ b/recipes-tools/schedtool-dl/schedtool-dl.bb
@@ -3,13 +3,17 @@ SECTION = "devel"
 LICENSE = "GPLv2"
 LIC_FILES_CHKSUM = "file://LICENSE;md5=dc1f51f7ca94aebffb9b3663d82873ec"
 
-SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git"
+SRC_URI = "git://github.com/jlelli/schedtool-dl.git;protocol=git \
+   
file://0001-schedtool-dl-add-flags-to-parameters-of-sched_setattr.patch \
+  "
 SRCREV = "3ffb479929c31cbae09de08f94f58b8f0f061d91"
 
 S = "${WORKDIR}/git"
 
 EXTRA_OEMAKE = "'CC=${CC}'"
 
+TARGET_CC_ARCH += "${LDFLAGS}"
+
 do_compile() {
oe_runmake
 }
diff --git 
a/recipes-tools/schedtool-dl/schedtool-dl/0001-schedtool-dl-add-flags-to-parameters-of-sched_setattr.patch
 
b/recipes-tools/schedtool-dl/schedtool-dl/0001-schedtool-dl-add-flags-to-parameters-of-sched_setattr.patch
new file mode 100644
index 000..65d5059
--- /dev/null
+++ 
b/recipes-tools/schedtool-dl/schedtool-dl/0001-schedtool-dl-add-flags-to-parameters-of-sched_setattr.patch
@@ -0,0 +1,56 @@
+From c75ae0f6ac2bb9eb893cce82e93144e1b3c36389 Mon Sep 17 00:00:00 2001
+From: Qi Hou 
+Date: Wed, 16 Mar 2016 05:44:40 +
+Subject: [PATCH] schedtool-dl: add flags to parameters of sched_setattr
+
+git://github.com/jlelli/schedtool-dl.git;protocol=git
+commit 3ffb479929c31cbae09de08f94f58b8f0f061d91
+
+The commit numbered as 3ffb479 has adapted to the very last changes to the 
ABI,except for the
+syscall of sched_setattr.
+
+While executing schedtool,there was an error,like below:
+
+root@128:/opt/wr-test/testcases/kts/edf# schedtool -E -t 8000:1 -e yes
+ERROR: could not set PID 1731 to E: SCHED_DEADLINE - value out of range / 
policy not implemented
+
+The cause of this case is that the syscall of sched_setattr is declared with 3 
parameters,but in
+the use of it in schedtool,there was only two parameters.So to adapt this 
declaration,we should
+add one more parameter,flags,when calling sched_setattr.
+
+In kernel source file kernel/sched/core.c,the declaration of the syscall of 
sched_setattr like below:
+/**
+ * sys_sched_setattr - same as above, but with extended sched_attr
+ * @pid: the pid in question.
+ * @uattr: structure containing the extended parameters.
+ * @flags: for future extension.
+ */
+ SYSCALL_DEFINE3(sched_setattr, pid_t, pid, struct sched_attr __user *, uattr,
+unsigned int, flags)
+ {
+   ...
+ }
+
+In schedtool-dl source file syscall_magic.h,the use of sched_setattr like 
below:
+syscall(__NR_sched_setattr, pid, attr)
+
+Upstream-Status: Backport
+
+Signed-off-by: Qi Hou 
+---
+ syscall_magic.h | 2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+diff --git a/syscall_magic.h b/syscall_magic.h
+index 7dcb967..2735dfb 100644
+--- a/syscall_magic.h
 b/syscall_magic.h
+@@ -76,4 +76,4 @@ struct sched_attr {
+   syscall(__NR_sched_getattr, pid, attr, size, flags)
+ 
+ #define sched_setattr(pid, attr, flags) \
+-  syscall(__NR_sched_setattr, pid, attr)
++  syscall(__NR_sched_setattr, pid, attr,flags)
+-- 
+1.9.1
+
-- 
2.8.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH] kernel: Fix config warning for CONFIG_I2C_ALGOBIT

2017-09-28 Thread zhe.he
From: He Zhe 

CONFIG_DRM in yocto-kernel-cache selects CONFIG_I2C_ALGOBIT as "y".
Change CONFIG_I2C_ALGOBIT 00026-lm-sensors.cfg from "m" to "y" to
avoid following config conflict.

-- CONFIG_I2C_ALGOBIT -
Config: CONFIG_I2C_ALGOBIT
From: /PATH/TO/i915.cfg /PATH/TO/00026-lm-sensors.cfg
Requested value:  CONFIG_I2C_ALGOBIT=m
Actual value: CONFIG_I2C_ALGOBIT=y

Signed-off-by: He Zhe 
---
 meta-cgl-common/recipes-kernel/linux/files/cfg/00026-lm-sensors.cfg | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git 
a/meta-cgl-common/recipes-kernel/linux/files/cfg/00026-lm-sensors.cfg 
b/meta-cgl-common/recipes-kernel/linux/files/cfg/00026-lm-sensors.cfg
index f28bdf6..71c4cad 100644
--- a/meta-cgl-common/recipes-kernel/linux/files/cfg/00026-lm-sensors.cfg
+++ b/meta-cgl-common/recipes-kernel/linux/files/cfg/00026-lm-sensors.cfg
@@ -1,5 +1,5 @@
 CONFIG_I2C_SMBUS=m
-CONFIG_I2C_ALGOBIT=m
+CONFIG_I2C_ALGOBIT=y
 CONFIG_I2C_ALGOPCA=m
 CONFIG_I2C_ALI1535=m
 CONFIG_I2C_ALI1563=m
-- 
2.8.1

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-dpdk][PATCH] dpdk: Fix do_compile failure for qemux86 and qemux86-64

2019-06-10 Thread zhe.he
From: He Zhe 

DPDK_TARGET_MACHINE in bbappend in other layers forms the dpdk-internal variable
MACHINE_CFLAGS which is passed to dpdk compilation command line containing the
first -march parameter. And EXTRA_CFLAGS in dpdk.inc is passed to dpdk command
line containing the second -march parameter. By mistake, the first -march had
always overwritten the second one until the following commit of GCC v9.1.0
8c0f695d83d1 ("driver: Also prune joined switches with negation").

Since it was fixed, the second -march, which was core2 for qemux86-64 or
core2-32 for qemux86, began to take effect. But core2* does not have SSE4.2
feature which is required by some dpdk instruction optimization and thus cause
the following compilation failure.

9.1.0/include/smmintrin.h:179:1: error: inlining failed in call to always_inline
'_mm_blendv_epi8': target specific option mismatch
  179 | _mm_blendv_epi8 (__m128i __X, __m128i __Y, __m128i __M)
  | ^~~

This patch adds DPDK_EXTRA_CFLAGS to append appropriate -march, corei7 which is
minimum and clear and independent of host machine, to dpdk compilation command
line to overwrite all previous ones, without having to change dpdk source code.

Note that as we do not want to change the default tune core2* for qemux86*, this
patch just fixes the compilation error. It would probably not be able to run on
qemux86* with corei7 tune.

Signed-off-by: He Zhe 
---
 recipes-extended/dpdk/dpdk.inc | 9 ++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index a0e081a..0275e0c 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -61,6 +61,9 @@ DPDK_RTE_TARGET_x86-64 = "x86_64-native-linuxapp-gcc"
 DPDK_RTE_TARGET_x86 = "i686-native-linuxapp-gcc"
 DPDK_RTE_TARGET_aarch64 = "arm64-${DPDK_TARGET_MACH}-linuxapp-gcc"
 export RTE_TARGET = "${DPDK_RTE_TARGET}"
+DPDK_EXTRA_CFLAGS = ""
+DPDK_EXTRA_CFLAGS_qemux86 ?= "-march=corei7"
+DPDK_EXTRA_CFLAGS_qemux86-64 ?= "-march=corei7"
 
 # The list of intel Comms platforms and their target machine
 # process mapping. The supported target machine is listed under
@@ -100,18 +103,18 @@ do_compile () {
 
cd ${S}/${RTE_TARGET}
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" \
   prefix=""  LDFLAGS="${TUNE_LDARGS}"  WERROR_FLAGS="-w" V=1
 
cd ${S}/examples/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
 
cd ${S}/test/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
${DPDK_EXTRA_CFLAGS} -I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/test/$@/"
 }
 
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-dpdk][PATCH] dpdk: mk: disable warning for packed member pointer

2019-06-10 Thread zhe.he
From: He Zhe 

Backport a patch from upstream to fix the following build failure.

x86_64-native-linuxapp-gcc/include/rte_ether.h:178:2: error:
converting a packed 'const struct ether_addr' pointer (alignment 1) to a 
'unaligned_uint16_t' {aka 'const short
 unsigned int'} pointer (alignment 2) may result in an unaligned pointer value 
[-Werror=address-of-packed-member]
|   178 |  const unaligned_uint16_t *ea_words = (const unaligned_uint16_t *)ea;
|   |  ^

Signed-off-by: He Zhe 
---
 ...disable-warning-for-packed-member-pointer.patch | 48 ++
 recipes-extended/dpdk/dpdk_17.11.3.bb  |  1 +
 2 files changed, 49 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
new file mode 100644
index 000..70a8dec
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
@@ -0,0 +1,48 @@
+From a385972c3675dd2b4792ab5b3cf7a536e6f9846c Mon Sep 17 00:00:00 2001
+From: Reshma Pattan 
+Date: Thu, 2 May 2019 10:33:34 +0100
+Subject: [PATCH] mk: disable warning for packed member pointer
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+gcc 9 on Fedora 30 gives an error
+"taking address of packed member may result in an
+unaligned pointer value" warnings.
+
+For clang builds this warning is already disabled,
+so disable "-Waddress-of-packed-member" for gcc builds
+also.
+
+Snippet of build error:
+lib/librte_eal/linux/eal/eal_memalloc.c: In function ‘alloc_seg_walk’:
+lib/librte_eal/linux/eal/eal_memalloc.c:768:12: error:
+taking address of packed member of ‘struct rte_mem_config’ may result
+in an unaligned pointer value [-Werror=address-of-packed-member]
+  768 |  cur_msl = &mcfg->memsegs[msl_idx];
+  |^~~
+
+Signed-off-by: Reshma Pattan 
+Tested-by: David Marchand 
+Upstream-Status: Backport
+Signed-off-by: He Zhe 
+---
+ mk/toolchain/gcc/rte.vars.mk | 3 +++
+ 1 file changed, 3 insertions(+)
+
+diff --git a/mk/toolchain/gcc/rte.vars.mk b/mk/toolchain/gcc/rte.vars.mk
+index d8b99fa..b852fcf 100644
+--- a/mk/toolchain/gcc/rte.vars.mk
 b/mk/toolchain/gcc/rte.vars.mk
+@@ -87,5 +87,8 @@ WERROR_FLAGS += -Wimplicit-fallthrough=2
+ WERROR_FLAGS += -Wno-format-truncation
+ endif
+ 
++# disable packed member unalign warnings
++WERROR_FLAGS += -Wno-address-of-packed-member
++
+ export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
+ export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
+-- 
+2.7.4
+
diff --git a/recipes-extended/dpdk/dpdk_17.11.3.bb 
b/recipes-extended/dpdk/dpdk_17.11.3.bb
index 7fc89d2..af42ad8 100644
--- a/recipes-extended/dpdk/dpdk_17.11.3.bb
+++ b/recipes-extended/dpdk/dpdk_17.11.3.bb
@@ -12,4 +12,5 @@ SRC_URI += "\
 file://dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch \
 file://dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch \
 file://dpdk-17.11-Fix-strncpy-error-for-GCC8.patch \
+file://dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch \
 "
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-dpdk][PATCH] dpdk: Remove 18.05

2019-06-25 Thread zhe.he
From: He Zhe 

We have already had 18.11 and 18.05 is not a stable version.

Signed-off-by: He Zhe 
---
 recipes-extended/dpdk/dpdk_18.05.bb | 15 ---
 1 file changed, 15 deletions(-)
 delete mode 100644 recipes-extended/dpdk/dpdk_18.05.bb

diff --git a/recipes-extended/dpdk/dpdk_18.05.bb 
b/recipes-extended/dpdk/dpdk_18.05.bb
deleted file mode 100644
index b6897a8..000
--- a/recipes-extended/dpdk/dpdk_18.05.bb
+++ /dev/null
@@ -1,15 +0,0 @@
-include dpdk.inc
-
-SRCREV = "a5dce6286cc56655320d975c67b0dbe08693"
-
-LICENSE = "BSD-3-Clause & LGPLv2.1 & GPLv2"
-LIC_FILES_CHKSUM = 
"file://license/gpl-2.0.txt;md5=b234ee4d69f5fce4486a80fdaf4a4263 \
-
file://license/lgpl-2.1.txt;md5=4b54a1fd55a448865a0b32d41598759d \
-
file://license/bsd-3-clause.txt;md5=0f00d99239d922ffd13cabef83b33444"
-
-SRC_URI += "\
-file://dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch \
-file://dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch \
-
file://dpdk-16.04-dpdk-enable-ip_fragmentation-in-common_base-config.patch \
-file://0001-examples-Fix-maybe-uninitialized-warning.patch \
-"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-security][PATCH] kernel: Add conditional inclusion of fragments for linux-yocto-dev

2019-06-26 Thread zhe.he
From: He Zhe 

Signed-off-by: He Zhe 
---
 recipes-kernel/linux/linux-yocto-dev.bbappend | 11 +++
 1 file changed, 11 insertions(+)
 create mode 100644 recipes-kernel/linux/linux-yocto-dev.bbappend

diff --git a/recipes-kernel/linux/linux-yocto-dev.bbappend 
b/recipes-kernel/linux/linux-yocto-dev.bbappend
new file mode 100644
index 000..68b2b8b
--- /dev/null
+++ b/recipes-kernel/linux/linux-yocto-dev.bbappend
@@ -0,0 +1,11 @@
+FILESEXTRAPATHS_prepend := "${THISDIR}/linux-yocto-5.0:"
+
+SRC_URI += "\
+${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' 
file://apparmor.cfg', '', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'apparmor', ' 
file://apparmor_on_boot.cfg', '', d)} \
+"
+
+SRC_URI += "\
+${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' file://smack.cfg', 
'', d)} \
+${@bb.utils.contains('DISTRO_FEATURES', 'smack', ' 
file://smack-default-lsm.cfg', '', d)} \
+"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-dpdk][PATCH v2] dpdk: Remove 18.05

2019-06-30 Thread zhe.he
From: He Zhe 

We have already had 18.11 and 18.05 is not a stable version.
This patch also removes the patch no longer needed.

Signed-off-by: He Zhe 
---
v2: Remove the patch no longer needed.

 ...2-dpdk-fix-installation-warning-and-issue.patch | 79 --
 recipes-extended/dpdk/dpdk_18.05.bb| 15 
 2 files changed, 94 deletions(-)
 delete mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch
 delete mode 100644 recipes-extended/dpdk/dpdk_18.05.bb

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch
deleted file mode 100644
index 0505888..000
--- 
a/recipes-extended/dpdk/dpdk/dpdk-17.02-dpdk-fix-installation-warning-and-issue.patch
+++ /dev/null
@@ -1,79 +0,0 @@
-From 0be350c3b04d83ea9182f45936ef3219aed5c0c1 Mon Sep 17 00:00:00 2001
-From: Shashwat Pandey 
-Date: Mon, 20 Feb 2017 15:46:22 +0800
-Subject: [PATCH] dpdk: fix installation warning and issue
-
-Upstream-Status: Inappropriate [configuration]
-
-Ensure that all compiled libs should be installed to correct location.
-For cross compiling cp -r and extra tar flags used to avoid  QA warning
-[host-user-contaminated].
-Added excluded files from bin and removing mk and app/dpdk-pmdinfogen files
-installation since it is not needed as a part of image.
-
-Signed-off-by: Shashwat Pandey 
-

- mk/rte.sdkinstall.mk | 29 ++---
- 1 file changed, 14 insertions(+), 15 deletions(-)
-
-diff --git a/mk/rte.sdkinstall.mk b/mk/rte.sdkinstall.mk
-index 4e97feff9fde..42625333a4e2 100644
 a/mk/rte.sdkinstall.mk
-+++ b/mk/rte.sdkinstall.mk
-@@ -115,16 +115,17 @@ endif
- 
- install-runtime:
-   $(Q)$(call rte_mkdir, $(DESTDIR)$(libdir))
--  $(Q)cp -a$O/lib/* $(DESTDIR)$(libdir)
-+  $(Q)cp -r$O/lib/* $(DESTDIR)$(libdir)
-   $(Q)$(call rte_mkdir, $(DESTDIR)$(bindir))
--  $(Q)tar -cf -  -C $O --exclude 'app/*.map' \
--  --exclude app/dpdk-pmdinfogen \
--  --exclude 'app/cmdline*' --exclude app/test \
--  --exclude app/testacl --exclude app/testpipeline app | \
--  tar -xf -  -C $(DESTDIR)$(bindir) --strip-components=1 \
--  --keep-newer-files
-+  $(Q)tar -cf -  -C $O --exclude app/dpdk-pmdinfogen app | \
-+  tar -xf -  -C $(DESTDIR)$(bindir) --no-same-owner 
--no-same-permissions \
-+  --strip-components=1 --keep-newer-files 
--warning=no-ignore-newer
-   $(Q)$(call rte_mkdir,  $(DESTDIR)$(datadir))
--  $(Q)cp -a $(RTE_SDK)/usertools $(DESTDIR)$(datadir)
-+  $(Q)cp -r $(RTE_SDK)/usertools $(DESTDIR)$(datadir)
-+  $(Q)$(call rte_symlink,
$(DESTDIR)$(datadir)/usertools/dpdk-setup.sh, \
-+ $(DESTDIR)$(datadir)/usertools/setup.sh)
-+  $(Q)$(call rte_symlink,
$(DESTDIR)$(datadir)/usertools/dpdk-devbind.py, \
-+ 
$(DESTDIR)$(datadir)/usertools/dpdk_nic_bind.py)
-   $(Q)$(call rte_mkdir,  $(DESTDIR)$(sbindir))
-   $(Q)$(call rte_symlink,
$(DESTDIR)$(datadir)/usertools/dpdk-devbind.py, \
-  $(DESTDIR)$(sbindir)/dpdk-devbind)
-@@ -142,7 +143,7 @@ endif
- install-kmod:
- ifneq ($(wildcard $O/kmod/*),)
-   $(Q)$(call rte_mkdir, $(DESTDIR)$(kerneldir))
--  $(Q)cp -a   $O/kmod/* $(DESTDIR)$(kerneldir)
-+  $(Q)cp -r   $O/kmod/* $(DESTDIR)$(kerneldir)
- endif
- 
- install-sdk:
-@@ -151,11 +152,9 @@ install-sdk:
-   tar -xf -  -C $(DESTDIR)$(includedir) --strip-components=1 \
-   --keep-newer-files
-   $(Q)$(call rte_mkdir,$(DESTDIR)$(sdkdir))
--  $(Q)cp -a   $(RTE_SDK)/mk$(DESTDIR)$(sdkdir)
--  $(Q)cp -a   $(RTE_SDK)/buildtools$(DESTDIR)$(sdkdir)
--  $(Q)$(call rte_mkdir,
$(DESTDIR)$(targetdir)/app)
--  $(Q)cp -a   $O/.config   $(DESTDIR)$(targetdir)
--  $(Q)cp -a   $O/app/dpdk-pmdinfogen   
$(DESTDIR)$(targetdir)/app
-+  $(Q)cp -r   $(RTE_SDK)/buildtools   $(DESTDIR)$(sdkdir)
-+  $(Q)$(call rte_mkdir,$(DESTDIR)$(targetdir))
-+  $(Q)cp -r   $O/.config   $(DESTDIR)$(targetdir)
-   $(Q)$(call rte_symlink, $(DESTDIR)$(includedir), 
$(DESTDIR)$(targetdir)/include)
-   $(Q)$(call rte_symlink, $(DESTDIR)$(libdir), 
$(DESTDIR)$(targetdir)/lib)
- 
-@@ -171,4 +170,4 @@ ifneq ($(wildcard $O/doc/*/*/*pdf),)
-   $(Q)cp -a $O/doc/*/*/*pdf $(DESTDIR)$(docdir)/guides
- endif
-   $(Q)$(call rte_mkdir, $(DESTDIR)$(datadir))
--  $(Q)cp -a $(RTE_SDK)/examples $(DESTDIR)$(datadir)
-+  $(Q)cp -r $(RTE_SDK)/examples $(DESTDIR)$(datadir)
diff --git a/recipes-extended/dpdk/dpdk_18.05.bb 
b/recipes-extended

[yocto] [meta-dpdk][PATCH] dpdk: Fix exmples and test _FORTIFY_SOURCE build failure

2019-07-10 Thread zhe.he
From: He Zhe 

When building examples and tests with GCC9, the following errors come up,

 error: #warning _FORTIFY_SOURCE requires compiling with optimization (-O) 
[-Werror=cpp]
  382 | #  warning _FORTIFY_SOURCE requires compiling with optimization (-O)
  |^~~
cc1: all warnings being treated as errors

dpdk itself already appends -O3 the EXTRA_CFLAGS for some of those cases, but
dpdk.inc overwrites EXTRA_CFLAGS when evoking make. This patches adds it back.

Signed-off-by: He Zhe 
---
 recipes-extended/dpdk/dpdk.inc | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index a0e081a..9dcec76 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -106,12 +106,12 @@ do_compile () {
 
cd ${S}/examples/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} -O3 
-I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/examples/$@/"
 
cd ${S}/test/
oe_runmake EXTRA_LDFLAGS="-L${STAGING_LIBDIR} --hash-style=gnu 
-fuse-ld=bfd" \
-  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} 
-I${STAGING_INCDIR}" \
+  EXTRA_CFLAGS="${HOST_CC_ARCH} ${TOOLCHAIN_OPTIONS} -O3 
-I${STAGING_INCDIR}" \
   CROSS="${TARGET_PREFIX}" O="${S}/test/$@/"
 }
 
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[linux-yocto] [PATCH] btrfs: Fix build error while LIBCRC32C is module

2019-07-25 Thread zhe.he
From: YueHaibing 

If CONFIG_BTRFS_FS is y and CONFIG_LIBCRC32C is m,
building fails:

  fs/btrfs/super.o: In function `btrfs_mount_root':
  super.c:(.text+0xb7f9): undefined reference to `crc32c_impl'
  fs/btrfs/super.o: In function `init_btrfs_fs':
  super.c:(.init.text+0x3465): undefined reference to `crc32c_impl'
  fs/btrfs/extent-tree.o: In function `hash_extent_data_ref':
  extent-tree.c:(.text+0xe60): undefined reference to `crc32c'
  extent-tree.c:(.text+0xe78): undefined reference to `crc32c'
  extent-tree.c:(.text+0xe8b): undefined reference to `crc32c'
  fs/btrfs/dir-item.o: In function `btrfs_insert_xattr_item':
  dir-item.c:(.text+0x291): undefined reference to `crc32c'
  fs/btrfs/dir-item.o: In function `btrfs_insert_dir_item':
  dir-item.c:(.text+0x429): undefined reference to `crc32c'

Select LIBCRC32C to fix it.

Reported-by: Hulk Robot 
Fixes: d5178578bcd4 ("btrfs: directly call into crypto framework for 
checksumming")
Reviewed-by: Johannes Thumshirn 
Signed-off-by: YueHaibing 
Reviewed-by: David Sterba 
Signed-off-by: David Sterba 

commit 314c4cd6d9e60b9412dcd1b1783a66532f91ea2d upstream

Signed-off-by: He Zhe 
---
 fs/btrfs/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/fs/btrfs/Kconfig b/fs/btrfs/Kconfig
index 212b4a8..38651fa 100644
--- a/fs/btrfs/Kconfig
+++ b/fs/btrfs/Kconfig
@@ -4,6 +4,7 @@ config BTRFS_FS
tristate "Btrfs filesystem support"
select CRYPTO
select CRYPTO_CRC32C
+   select LIBCRC32C
select ZLIB_INFLATE
select ZLIB_DEFLATE
select LZO_COMPRESS
-- 
2.7.4

-- 
___
linux-yocto mailing list
linux-yo...@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


[yocto] [meta-dpdk][PATCH] dpdk: igb_uio: fix build on Linux 5.3 for fall through

2019-08-05 Thread zhe.he
From: He Zhe 

Since kernel v5.3 "-Wimplicit-fallthrough=3" gcc flag is enabled by default by
a035d552a93b ("Makefile: Globally enable fall-through warning") and would cause
the following build failure.

x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:248:
6: error: this statement may fall through [-Werror=implicit-fallthrough=]

Backport a patch from upstream and adjust context respectively for v17 and v18.
c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d

Signed-off-by: He Zhe 
---
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 81 ++
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 80 +
 recipes-extended/dpdk/dpdk_17.11.6.bb  |  1 +
 recipes-extended/dpdk/dpdk_18.11.2.bb  |  4 ++
 4 files changed, 166 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..90901eb
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,81 @@
+From c0307019689d5f8b4d5ca7d92a5585c94088afeb Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci_enable_interrupts’:
+   kernel/linux/igb_uio/igb_uio.c:230:6:
+   error: this statement may fall through
+   [-Werror=implicit-fallthrough=]
+  230 |   if (pci_alloc_irq_vectors(udev->pdev, 1, 1, 
+kernel/linux/igb_uio/igb_uio.c:240:2: note: here
+  240 |  case RTE_INTR_MODE_MSI:
+  |  ^~~~
+
+The build error is caused by Linux kernel commit in 5.3 that enables the
+"-Wimplicit-fallthrough=3" gcc flag.
+Commit a035d552a93b ("Makefile: Globally enable fall-through warning")
+
+To fix the error, either a gcc attribute can be provided [1] or a code
+comment with some defined syntax need to be provided [2], since there is
+already comments, updated them slightly to match the required syntax to
+fix the build error.
+
+[1]
+"__attribute__ ((fallthrough));"
+
+[2]
+[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?
+fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?
+
+Cc: sta...@dpdk.org
+
+Signed-off-by: Ferruh Yigit 
+
+commit c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d upstream
+Adjust code context
+
+Signed-off-by: He Zhe 
+---
+ lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c 
b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+index 45d7027..3073bca 100644
+--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
 b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+@@ -254,7 +254,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   }
+ #endif
+ 
+-  /* fall back to MSI */
++  /* falls through - to MSI */
+   case RTE_INTR_MODE_MSI:
+ #ifndef HAVE_ALLOC_IRQ_VECTORS
+   if (pci_enable_msi(udev->pdev) == 0) {
+@@ -273,7 +273,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+ #endif
+-  /* fall back to INTX */
++  /* falls through - to INTX */
+   case RTE_INTR_MODE_LEGACY:
+   if (pci_intx_mask_supported(udev->pdev)) {
+   dev_dbg(&udev->pdev->dev, "using INTX");
+@@ -283,7 +283,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+   dev_notice(&udev->pdev->dev, "PCI INTX mask not supported\n");
+-  /* fall back to no IRQ */
++  /* falls through - to no IRQ */
+   case RTE_INTR_MODE_NONE:
+   udev->mode = RTE_INTR_MODE_NONE;
+   udev->info.irq = UIO_IRQ_NONE;
+-- 
+2.7.4
+
diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..417d93b
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,80 @@
+From af89b90b4e5e9d1533b6debd86ae38bbd82df8c8 Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci

[yocto] [meta-dpdk][PATCH] dpdk: igb_uio: fix build on Linux 5.3 for fall through

2019-08-05 Thread zhe.he
From: He Zhe 

Since kernel v5.3 "-Wimplicit-fallthrough=3" gcc flag is enabled by default by
a035d552a93b ("Makefile: Globally enable fall-through warning") and would cause
the following build failure.

x86_64-native-linuxapp-gcc/build/lib/librte_eal/linuxapp/igb_uio/igb_uio.c:248:
6: error: this statement may fall through [-Werror=implicit-fallthrough=]

Backport a patch from upstream and adjust context respectively for v17 and v18.
c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d

Signed-off-by: He Zhe 
---
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 81 ++
 ...o-fix-build-on-Linux-5.3-for-fall-through.patch | 80 +
 recipes-extended/dpdk/dpdk_17.11.6.bb  |  1 +
 recipes-extended/dpdk/dpdk_18.11.2.bb  |  4 ++
 4 files changed, 166 insertions(+)
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 create mode 100644 
recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..94310dd
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,81 @@
+From c0307019689d5f8b4d5ca7d92a5585c94088afeb Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function ‘igbuio_pci_enable_interrupts’:
+   kernel/linux/igb_uio/igb_uio.c:230:6:
+   error: this statement may fall through
+   [-Werror=implicit-fallthrough=]
+  230 |   if (pci_alloc_irq_vectors(udev->pdev, 1, 1, 
+kernel/linux/igb_uio/igb_uio.c:240:2: note: here
+  240 |  case RTE_INTR_MODE_MSI:
+  |  ^~~~
+
+The build error is caused by Linux kernel commit in 5.3 that enables the
+"-Wimplicit-fallthrough=3" gcc flag.
+Commit a035d552a93b ("Makefile: Globally enable fall-through warning")
+
+To fix the error, either a gcc attribute can be provided [1] or a code
+comment with some defined syntax need to be provided [2], since there is
+already comments, updated them slightly to match the required syntax to
+fix the build error.
+
+[1]
+"__attribute__ ((fallthrough));"
+
+[2]
+[ \t.!]*([Ee]lse,? |[Ii]ntentional(ly)? )?
+fall(s | |-)?thr(ough|u)[ \t.!]*(-[^\n\r]*)?
+
+Cc: sta...@dpdk.org
+
+Signed-off-by: Ferruh Yigit 
+
+Upstream-Status: Backport[c96bbbd010f7abb88c2ca2ed9dfc5ecd37e9027d]
+Adjust code context
+
+Signed-off-by: He Zhe 
+---
+ lib/librte_eal/linuxapp/igb_uio/igb_uio.c | 6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+diff --git a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c 
b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+index 45d7027..3073bca 100644
+--- a/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
 b/lib/librte_eal/linuxapp/igb_uio/igb_uio.c
+@@ -254,7 +254,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   }
+ #endif
+ 
+-  /* fall back to MSI */
++  /* falls through - to MSI */
+   case RTE_INTR_MODE_MSI:
+ #ifndef HAVE_ALLOC_IRQ_VECTORS
+   if (pci_enable_msi(udev->pdev) == 0) {
+@@ -273,7 +273,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+ #endif
+-  /* fall back to INTX */
++  /* falls through - to INTX */
+   case RTE_INTR_MODE_LEGACY:
+   if (pci_intx_mask_supported(udev->pdev)) {
+   dev_dbg(&udev->pdev->dev, "using INTX");
+@@ -283,7 +283,7 @@ igbuio_pci_enable_interrupts(struct rte_uio_pci_dev *udev)
+   break;
+   }
+   dev_notice(&udev->pdev->dev, "PCI INTX mask not supported\n");
+-  /* fall back to no IRQ */
++  /* falls through - to no IRQ */
+   case RTE_INTR_MODE_NONE:
+   udev->mode = RTE_INTR_MODE_NONE;
+   udev->info.irq = UIO_IRQ_NONE;
+-- 
+2.7.4
+
diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
new file mode 100644
index 000..3222a3c
--- /dev/null
+++ 
b/recipes-extended/dpdk/dpdk/dpdk-18.11-igb_uio-fix-build-on-Linux-5.3-for-fall-through.patch
@@ -0,0 +1,80 @@
+From af89b90b4e5e9d1533b6debd86ae38bbd82df8c8 Mon Sep 17 00:00:00 2001
+From: Ferruh Yigit 
+Date: Mon, 29 Jul 2019 13:32:16 +0100
+Subject: [PATCH] igb_uio: fix build on Linux 5.3 for fall through
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+build error:
+kernel/linux/igb_uio/igb_uio.c:
+   In function 

[yocto] [meta-dpdk][PATCH] dpdk: Skip build if necessary kernel options is not included

2019-09-16 Thread zhe.he
From: He Zhe 

dpdk depends on some kernel configuration options without which it is not able
to successfully build.

Signed-off-by: He Zhe 
---
 recipes-extended/dpdk/dpdk.inc | 5 +
 1 file changed, 5 insertions(+)

diff --git a/recipes-extended/dpdk/dpdk.inc b/recipes-extended/dpdk/dpdk.inc
index 3b997eb..9c9b397 100644
--- a/recipes-extended/dpdk/dpdk.inc
+++ b/recipes-extended/dpdk/dpdk.inc
@@ -1,6 +1,11 @@
 DESCRIPTION = "Intel(r) Data Plane Development Kit"
 HOMEPAGE = "http://dpdk.org";
 
+python () {
+if not bb.utils.contains('KERNEL_FEATURES', 
'features/intel-dpdk/intel-dpdk.scc', True, False, d):
+raise bb.parse.SkipPackage("dpdk requires 
features/intel-dpdk/intel-dpdk.scc in KERNEL_FEATURES to build")
+}
+
 STABLE = ""
 BRANCH = "master"
 S = "${WORKDIR}/git"
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-dpdk][PATCH] [RFC] dpdk: Remove v17

2019-09-23 Thread zhe.he
From: He Zhe 

openvswith used not to be able to work with dpdk v18. That's one of the reasons
why we keep v17. Now that openvswitch in meta-virtulization has been upgraded to
v2.11, officially claimed support of dpdk18, we can drop dpdk v17.

Signed-off-by: He Zhe 
---
 ...dk-16.07-dpdk-fix-for-parellel-make-issue.patch | 40 --
 ...disable-warning-for-packed-member-pointer.patch | 48 --
 recipes-extended/dpdk/dpdk_17.11.6.bb  | 19 -
 3 files changed, 107 deletions(-)
 delete mode 100644 
recipes-extended/dpdk/dpdk/dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch
 delete mode 100644 
recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
 delete mode 100644 recipes-extended/dpdk/dpdk_17.11.6.bb

diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch 
b/recipes-extended/dpdk/dpdk/dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch
deleted file mode 100644
index 55f0c15..000
--- 
a/recipes-extended/dpdk/dpdk/dpdk-16.07-dpdk-fix-for-parellel-make-issue.patch
+++ /dev/null
@@ -1,40 +0,0 @@
-From 4a86048d44cae812b227b857772aeeb839502706 Mon Sep 17 00:00:00 2001
-From: Rahul Kumar Gupta 
-Date: Fri, 2 Sep 2016 15:48:52 +0800
-Subject: [PATCH] dpdk: fix for parellel make issue
-
-To make sure that the path of libraries should be correct and
-libraries will be build before, And available at the time of
-linking example apps.
-
-Signed-off-by: Rahul Kumar Gupta 
-

- examples/Makefile | 1 +
- examples/ethtool/ethtool-app/Makefile | 1 +
- 2 files changed, 2 insertions(+)
-
-diff --git a/examples/Makefile b/examples/Makefile
-index 17ecf7f64cda..2a8e805b85a7 100644
 a/examples/Makefile
-+++ b/examples/Makefile
-@@ -41,6 +41,7 @@ DIRS-$(CONFIG_RTE_LIBRTE_BBDEV) += bbdev_app
- DIRS-$(CONFIG_RTE_LIBRTE_PMD_BOND) += bond
- DIRS-y += cmdline
- DIRS-$(CONFIG_RTE_LIBRTE_DISTRIBUTOR) += distributor
-+DEPDIRS-y += examples/ethtool/lib
- DIRS-y += ethtool
- DIRS-y += exception_path
- DIRS-$(CONFIG_RTE_LIBRTE_EFD) += server_node_efd
-diff --git a/examples/ethtool/ethtool-app/Makefile 
b/examples/ethtool/ethtool-app/Makefile
-index 4cd9efdd574b..d3c709ab2fef 100644
 a/examples/ethtool/ethtool-app/Makefile
-+++ b/examples/ethtool/ethtool-app/Makefile
-@@ -19,6 +19,7 @@ SRCS-y := main.c ethapp.c
- CFLAGS += -O3 -D_GNU_SOURCE -pthread -I$(SRCDIR)/../lib
- CFLAGS += $(WERROR_FLAGS)
- 
-+LDLIBS += -L$(ETHTOOL_LIB_PATH)/
- LDLIBS += -L$(subst ethtool-app,lib,$(RTE_OUTPUT))/lib
- LDLIBS += -lrte_ethtool
- 
diff --git 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
 
b/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
deleted file mode 100644
index 70a8dec..000
--- 
a/recipes-extended/dpdk/dpdk/dpdk-17.11-mk-disable-warning-for-packed-member-pointer.patch
+++ /dev/null
@@ -1,48 +0,0 @@
-From a385972c3675dd2b4792ab5b3cf7a536e6f9846c Mon Sep 17 00:00:00 2001
-From: Reshma Pattan 
-Date: Thu, 2 May 2019 10:33:34 +0100
-Subject: [PATCH] mk: disable warning for packed member pointer
-MIME-Version: 1.0
-Content-Type: text/plain; charset=UTF-8
-Content-Transfer-Encoding: 8bit
-
-gcc 9 on Fedora 30 gives an error
-"taking address of packed member may result in an
-unaligned pointer value" warnings.
-
-For clang builds this warning is already disabled,
-so disable "-Waddress-of-packed-member" for gcc builds
-also.
-
-Snippet of build error:
-lib/librte_eal/linux/eal/eal_memalloc.c: In function ‘alloc_seg_walk’:
-lib/librte_eal/linux/eal/eal_memalloc.c:768:12: error:
-taking address of packed member of ‘struct rte_mem_config’ may result
-in an unaligned pointer value [-Werror=address-of-packed-member]
-  768 |  cur_msl = &mcfg->memsegs[msl_idx];
-  |^~~
-
-Signed-off-by: Reshma Pattan 
-Tested-by: David Marchand 
-Upstream-Status: Backport
-Signed-off-by: He Zhe 

- mk/toolchain/gcc/rte.vars.mk | 3 +++
- 1 file changed, 3 insertions(+)
-
-diff --git a/mk/toolchain/gcc/rte.vars.mk b/mk/toolchain/gcc/rte.vars.mk
-index d8b99fa..b852fcf 100644
 a/mk/toolchain/gcc/rte.vars.mk
-+++ b/mk/toolchain/gcc/rte.vars.mk
-@@ -87,5 +87,8 @@ WERROR_FLAGS += -Wimplicit-fallthrough=2
- WERROR_FLAGS += -Wno-format-truncation
- endif
- 
-+# disable packed member unalign warnings
-+WERROR_FLAGS += -Wno-address-of-packed-member
-+
- export CC AS AR LD OBJCOPY OBJDUMP STRIP READELF
- export TOOLCHAIN_CFLAGS TOOLCHAIN_LDFLAGS TOOLCHAIN_ASFLAGS
--- 
-2.7.4
-
diff --git a/recipes-extended/dpdk/dpdk_17.11.6.bb 
b/recipes-extended/dpdk/dpdk_17.11.6.bb
deleted file mode 100644
index 01bacd6..000
--- a/recipes-extended/dpdk/dpdk_17.11.6.bb
+++ /dev/null
@@ -1,19 +0,0 @@
-include dpdk.inc
-
-STABLE = "-stable"
-BRANCH = "17.11"
-SRCREV = "63d5c53b845d8360c0106374ce76eef9b5478c60"
-
-LICENSE = "LGPLv2 & GPLv2"
-LIC_FILES_CHKSUM = "file://LICENSE.GPL;md5=751419260aa954499f7abaabaa882bbe\

[yocto] [meta-selinux][PATCH] kernel: Remove non-existing kernel option

2019-10-24 Thread zhe.he
From: He Zhe 

CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION has been remove from mainline kernel
by the commit 4c145dce2601 ("xfrm: make xfrm modes builtin").

Signed-off-by: He Zhe 
---
 recipes-kernel/linux/files/selinux.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-kernel/linux/files/selinux.cfg 
b/recipes-kernel/linux/files/selinux.cfg
index 2edd366..7d16dc5 100644
--- a/recipes-kernel/linux/files/selinux.cfg
+++ b/recipes-kernel/linux/files/selinux.cfg
@@ -23,7 +23,6 @@ CONFIG_SECURITYFS=y
 CONFIG_SECURITY_NETWORK=y
 CONFIG_SECURITY_SELINUX=y
 CONFIG_SECURITY_SELINUX_BOOTPARAM=y
-CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
 CONFIG_SECURITY_SELINUX_DISABLE=y
 CONFIG_SECURITY_SELINUX_DEVELOP=y
 CONFIG_SECURITY_SELINUX_AVC_STATS=y
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH] kernel: Remove non-existing kernel option

2019-10-24 Thread zhe.he
From: He Zhe 

CONFIG_INET6_XFRM_MODE_ROUTEOPTIMIZATION has been removed from mainline kernel
by commit 4c145dce2601 ("xfrm: make xfrm modes builtin").

Signed-off-by: He Zhe 
---
 meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg 
b/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
index 1efd63e..b10b839 100644
--- a/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
+++ b/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
@@ -19,7 +19,6 @@ CONFIG_REISERFS_FS_SECURITY=y
 CONFIG_JFFS2_FS_SECURITY=y
 CONFIG_SECURITYFS=y
 CONFIG_SECURITY_SELINUX_BOOTPARAM=y
-CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
 CONFIG_SECURITY_SELINUX_DISABLE=y
 CONFIG_SECURITY_SELINUX_DEVELOP=y
 CONFIG_SECURITY_SELINUX_AVC_STATS=y
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-cgl][PATCH v2] kernel: Remove non-existing kernel option

2019-10-24 Thread zhe.he
From: He Zhe 

CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE has been removed from mainline kernel
by commit be6ec88f41ba ("selinux: Remove SECURITY_SELINUX_BOOTPARAM_VALUE").

Signed-off-by: He Zhe 
---
 meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg 
b/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
index 1efd63e..b10b839 100644
--- a/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
+++ b/meta-cgl-common/recipes-kernel/linux/files/cfg/00014-selinux.cfg
@@ -19,7 +19,6 @@ CONFIG_REISERFS_FS_SECURITY=y
 CONFIG_JFFS2_FS_SECURITY=y
 CONFIG_SECURITYFS=y
 CONFIG_SECURITY_SELINUX_BOOTPARAM=y
-CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
 CONFIG_SECURITY_SELINUX_DISABLE=y
 CONFIG_SECURITY_SELINUX_DEVELOP=y
 CONFIG_SECURITY_SELINUX_AVC_STATS=y
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


[yocto] [meta-selinux][PATCH v2] kernel: Remove non-existing kernel option

2019-10-24 Thread zhe.he
From: He Zhe 

CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE has been remove from mainline kernel
by the commit be6ec88f41ba ("selinux: Remove SECURITY_SELINUX_BOOTPARAM_VALUE").

Signed-off-by: He Zhe 
---
 recipes-kernel/linux/files/selinux.cfg | 1 -
 1 file changed, 1 deletion(-)

diff --git a/recipes-kernel/linux/files/selinux.cfg 
b/recipes-kernel/linux/files/selinux.cfg
index 2edd366..7d16dc5 100644
--- a/recipes-kernel/linux/files/selinux.cfg
+++ b/recipes-kernel/linux/files/selinux.cfg
@@ -23,7 +23,6 @@ CONFIG_SECURITYFS=y
 CONFIG_SECURITY_NETWORK=y
 CONFIG_SECURITY_SELINUX=y
 CONFIG_SECURITY_SELINUX_BOOTPARAM=y
-CONFIG_SECURITY_SELINUX_BOOTPARAM_VALUE=1
 CONFIG_SECURITY_SELINUX_DISABLE=y
 CONFIG_SECURITY_SELINUX_DEVELOP=y
 CONFIG_SECURITY_SELINUX_AVC_STATS=y
-- 
2.7.4

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto