[Xenomai] _X86_VSYSCALL on arm ?

[Xenomai] _X86_VSYSCALL on arm ?

[Hänel-Baas, Alexander]

Hi,

our xenomai application shows CONFIG_XENO_X86_VSYSCALL=1, but is is running on arm machine.

We compile the app on a debian x86 host machine with the OSELAS.Toolchain-2016.06 (arm-v7a-linux-gnueabi) for 
running on the arm Layerscape (ls1021a) target.
To get the proper clfags we ask xeno-config with "--skin=alchemy --cflags".

My issue :
Is CONFIG_XENO_X86_VSYSCALL=1 for an arm binary good?
Where is the step to configure this flag? 

When I pass --dump-config to the app, the following config was shown:

./g3t_rtdm_alex_test --dump-config
based on Xenomai/cobalt v3.0.3
CONFIG_MMU=1
CONFIG_SMP=1
CONFIG_XENO_BUILD_ARGS=" 'CFLAGS=-march=armv7-a -mfpu=vfp3 -D_FILE_OFFSET_BITS=64 -Wno-error=old-style-declaration -Wno-error=discarded-qualifiers' '--host=arm-v7a-linux-gnueabi' '--build=i686-host-linux-gnu' '--enable-pshared' '--enable-smp' '--disable-tls' '--enable-dlopen-libs' '--disable-doc-install' 'build_alias=i686-host-linux-gnu' 'host_alias=arm-v7a-linux-gnueabi' 'CC=arm-v7a-linux-gnueabi-gcc' 'CPP=arm-v7a-linux-gnueabi-cpp' 'PKG_CONFIG=/opt/g3DevelBase/g3Toolchain/g3Bsp/sd3XenoArmLs.Bsp.V2/platform-sm-arm/sysroot-cross/bin/arm-v7a-linux-gnueabi-pkg-config' 'PKG_CONFIG_PATH=''PKG_CONFIG_LIBDIR=/opt/g3DevelBase/g3Toolchain/g3Bsp/sd3XenoArmLs.Bsp.V2/platform-sm-arm/sysroot target/lib/pkgconfig:/opt/g3DevelBase/g3Toolchain/g3Bsp/sd3XenoArmLs.Bsp.V2/platform-sm-arm/sysroot-target/usr/lib/pkgconfig:/opt/g3DevelBase/g3Toolchain/g3Bsp/sd3XenoArmLs.Bsp.V2/platform-sm-arm/sysroot-target/share/pkgconfig:/opt/g3DevelBase/g3Toolchain/g3Bsp/sd3XenoArmLs.Bsp.V2/platform-sm-arm/sysroot-target/usr/share/pkgconfig'"
CONFIG_XENO_BUILD_STRING="i686-host-linux-gnu"
CONFIG_XENO_COBALT=1
CONFIG_XENO_COMPILER="gcc version 5.4.0 (OSELAS.Toolchain-2016.06.0) "
CONFIG_XENO_DEFAULT_PERIOD=1000000
CONFIG_XENO_FORTIFY=1
CONFIG_XENO_HOST_STRING="arm-v7a-linux-gnueabi"
CONFIG_XENO_LIBS_DLOPEN=1
CONFIG_XENO_LORES_CLOCK_DISABLED=1
CONFIG_XENO_PREFIX="/usr/xenomai"
CONFIG_XENO_PSHARED=1
CONFIG_XENO_RAW_CLOCK_ENABLED=1
CONFIG_XENO_REVISION_LEVEL=3
CONFIG_XENO_SANITY=1
CONFIG_XENO_TLSF=1
CONFIG_XENO_TLS_MODEL="global-dynamic"
CONFIG_XENO_UAPI_LEVEL=14
CONFIG_XENO_VERSION_MAJOR=3
CONFIG_XENO_VERSION_MINOR=0
CONFIG_XENO_VERSION_NAME="Groovy Cosmic Halo"
CONFIG_XENO_VERSION_STRING="3.0.3"
CONFIG_XENO_X86_VSYSCALL=1
---
CONFIG_XENO_ASYNC_CANCEL is OFF
CONFIG_XENO_COPPERPLATE_CLOCK_RESTRICTED is OFF
CONFIG_XENO_DEBUG is OFF
CONFIG_XENO_DEBUG_FULL is OFF
CONFIG_XENO_MERCURY is OFF
CONFIG_XENO_REGISTRY is OFF
CONFIG_XENO_REGISTRY_ROOT is OFF
CONFIG_XENO_VALGRIND_API is OFF
CONFIG_XENO_WORKAROUND_CONDVAR_PI is OFF
---
PTHREAD_STACK_DEFAULT=65536
AUTOMATIC_BOOTSTRAP=1


regards
Alexander Hänel-Baas

Re: [Xenomai] _X86_VSYSCALL on arm ?

[Jan Kiszka]

On 2017-03-30 09:32, Hänel-Baas, Alexander wrote:
> Hi,
> 
> our xenomai application shows CONFIG_XENO_X86_VSYSCALL=1, but is is running on arm machine.
> 
> We compile the app on a debian x86 host machine with the OSELAS.Toolchain-2016.06 (arm-v7a-linux-gnueabi) for 
> running on the arm Layerscape (ls1021a) target.
> To get the proper clfags we ask xeno-config with "--skin=alchemy --cflags".
> 
> My issue :
> Is CONFIG_XENO_X86_VSYSCALL=1 for an arm binary good?
> Where is the step to configure this flag? 

This had no effect on ARM. It was defined by default in configure[.ac],
even on non-x86, but that was fixed as a side effect of 18493575. You
will get this with the next latest stable 3.0.x release.

Jan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: OpenPGP digital signature
URL: <http://xenomai.org/pipermail/xenomai/attachments/20170330/c0ffef2c/attachment.sig>

Re: [Xenomai] _X86_VSYSCALL on arm ?

[Hänel-Baas, Alexander]

Hi Jan,

Thanks for your fast response.

> This had no effect on ARM. It was defined by default in configure[.ac], even on non-x86, but that was fixed as a side effect of 18493575. You will get this with the next latest stable 3.0.x release.

Nice to hear it. I had already expected that. 

By 
Alexander

-----Ursprüngliche Nachricht-----
Von: Jan Kiszka [mailto:jan.kiszka@web.de] 
Gesendet: Donnerstag, 30. März 2017 10:42
An: Hänel-Baas, Alexander; xenomai@xenomai.org
Betreff: Re: _X86_VSYSCALL on arm ?

On 2017-03-30 09:32, Hänel-Baas, Alexander wrote:
> Hi,
> 
> our xenomai application shows CONFIG_XENO_X86_VSYSCALL=1, but is is running on arm machine.
> 
> We compile the app on a debian x86 host machine with the 
> OSELAS.Toolchain-2016.06 (arm-v7a-linux-gnueabi) for running on the arm Layerscape (ls1021a) target.
> To get the proper clfags we ask xeno-config with "--skin=alchemy --cflags".
> 
> My issue :
> Is CONFIG_XENO_X86_VSYSCALL=1 for an arm binary good?
> Where is the step to configure this flag? 

This had no effect on ARM. It was defined by default in configure[.ac], even on non-x86, but that was fixed as a side effect of 18493575. You will get this with the next latest stable 3.0.x release.

Jan