run_kselftests.sh contains randomly spurious lines starting by "make[1]:".
The way the script is generated is most likely broken.
Until, we've got a proper fix, get rid of the lines after the generated
script is installed.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Recursive makefile is broken because it's using the same TARGETS variable
as selftests topdir and prevent to build futex functional tests:
make[2]: Nothing to be done for `all'.
Rename the variable to F_TARGETS in the futex functional tests Makefile.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Use the same fixup as used for timers test:
use LDLIBS to properly link against libpthread.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
sigaltstack was not using TEST_PROGS resulting in binary not being installed
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cc: Fathi Boudra <fathi.boudra@linaro.org>
* Adjust md5sum/sha256sum for the updated tarball
* Add libpcap dependency, needed by vm/mlock-random-test
* Rewrite TARGETS as a list (easier to copy/paste/update) and filter out
arch specific tests using bb.utils.contains_any()
* Add new tests introduced with 4.9 : capabilities, futex, lib,
membarrier, nsfs, pstore, seccomp, sigalstack, static_keys, zram.
* Adjust the packages list for the new tests.
Signed-off-by: Fathi Boudra <fathi.boudra@linaro.org>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Update to ti2017.00-rc2 tag as well as 4.9.13 kernel
revision
Signed-off-by: Dan Murphy <dmurphy@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cleaning up redefinition of mpm areas and moving to use what is defined
in the base device tree files as is.
This effectively changes to a new memory partition.
Note that this change needs a corresponding change in the dts files in
the kernel tree to adjust the mpm memory area to the new memory
partition.
The CMEM areas here are adjusted such that there is no overlap with the
mpm areas defined in the dts files in the kernel tree.
Note also the address ranges are arranged differently for K2G compared
to the other Keystone platforms.
(This is to accomodate common memory map for multiple k2g platforms)
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Cleaning up redefinition of mpm areas and moving to use what is defined
in the base device tree files as is.
This effectively changes to a new memory partition.
Note that this change needs a corresponding change in the dts files in
the kernel tree to adjust the mpm memory area to the new memory
partition.
The CMEM areas here are adjusted such that there is no overlap with the
mpm areas defined in the dts files in the kernel tree.
Also fixes issue with K2L, by removing overlapping memory area section.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
cmem.dtsi splits the already defined dsp_common_mpm_area DDR memory into
a smaller MPM segment and other CMEM blocks.
The mpm_block_mem is removed and instead the original memory sections
dsp_common_mpm_area and mpm_mem in the kernel dtb are updated to reflect
On the MSMC memory, cmem.dtsi defines a sram subnode instead of the
reserved memory.
mpm MSMC areas are already captured in the kernel dtb.
Signed-off-by: Sam Nelson <sam.nelson@ti.com>
Signed-off-by: Denys Dmytriyenko <denys@ti.com>
Dan Murphy
Denys Dmytriyenko
Fathi Boudra
Sam Nelson
Jacob Stiffler