[jh-images][PATCH 13/13] Update to Debian buster

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

Buster brings gcc 8, and that means we need the related patch for
Jailhouse 0.11.

The non-root-initramfs has to be switches to newer rules format that
allows to disable fakeroot reliably (to avoid the nesting issue).

And the orangepi target can drop the u-boot backport pick - injecting
additional apt sources via the machine conf was broken anyway and would
have exploded when adding a second ARM target.

Signed-off-by: Jan Kiszka 
---
 conf/distro/jailhouse-demo.conf|  2 +-
 conf/machine/orangepi-zero.conf|  3 --
 conf/machine/preferences.orangepi-zero.conf|  7 ---
 .../non-root-initramfs/files/debian/control|  3 +-
 recipes-core/non-root-initramfs/files/debian/rules | 10 +---
 .../files/0001-arm-Fix-build-with-gcc-8.patch  | 56 ++
 recipes-jailhouse/jailhouse/jailhouse_0.11.bb  |  3 +-
 7 files changed, 62 insertions(+), 22 deletions(-)
 delete mode 100644 conf/machine/preferences.orangepi-zero.conf
 create mode 100644 
recipes-jailhouse/jailhouse/files/0001-arm-Fix-build-with-gcc-8.patch

diff --git a/conf/distro/jailhouse-demo.conf b/conf/distro/jailhouse-demo.conf
index faf2455..93bd0a1 100644
--- a/conf/distro/jailhouse-demo.conf
+++ b/conf/distro/jailhouse-demo.conf
@@ -9,7 +9,7 @@
 # SPDX-License-Identifier: MIT
 #
 
-require conf/distro/debian-stretch.conf
+require conf/distro/debian-buster.conf
 
 KERNEL_NAME ?= "jailhouse"
 
diff --git a/conf/machine/orangepi-zero.conf b/conf/machine/orangepi-zero.conf
index 8d6c134..fb7bb2e 100644
--- a/conf/machine/orangepi-zero.conf
+++ b/conf/machine/orangepi-zero.conf
@@ -14,7 +14,4 @@ DISTRO_ARCH = "armhf"
 IMAGE_TYPE = "wic-img"
 IMAGER_INSTALL += "u-boot-sunxi"
 
-DISTRO_APT_SOURCES_append = " conf/distro/debian-buster.list"
-DISTRO_APT_PREFERENCES += "conf/machine/preferences.orangepi-zero.conf"
-
 IMAGE_INSTALL += "u-boot-script xradio-${KERNEL_NAME}"
diff --git a/conf/machine/preferences.orangepi-zero.conf 
b/conf/machine/preferences.orangepi-zero.conf
deleted file mode 100644
index 0bdd9ec..000
--- a/conf/machine/preferences.orangepi-zero.conf
+++ /dev/null
@@ -1,7 +0,0 @@
-Package: u-boot*
-Pin: release n=buster
-Pin-Priority: 501
-
-Package: *
-Pin: release n=buster
-Pin-Priority: -1
diff --git a/recipes-core/non-root-initramfs/files/debian/control 
b/recipes-core/non-root-initramfs/files/debian/control
index 059fb16..5ff2c5c 100644
--- a/recipes-core/non-root-initramfs/files/debian/control
+++ b/recipes-core/non-root-initramfs/files/debian/control
@@ -1,9 +1,10 @@
 Source: non-root-initramfs
 Section: misc
 Priority: optional
-Standards-Version: 3.9.6
+Standards-Version: 4.3.0
 Build-Depends: wget, cpio, unzip, rsync, python:native, bc
 Maintainer: Jan Kiszka 
+Rules-Requires-Root: no
 
 Package: non-root-initramfs
 Architecture: any
diff --git a/recipes-core/non-root-initramfs/files/debian/rules 
b/recipes-core/non-root-initramfs/files/debian/rules
index 0f7f079..6f2638b 100755
--- a/recipes-core/non-root-initramfs/files/debian/rules
+++ b/recipes-core/non-root-initramfs/files/debian/rules
@@ -13,22 +13,14 @@
 DPKG_EXPORT_BUILDFLAGS = 1
 include /usr/share/dpkg/default.mk
 
-build-image:
+override_dh_auto_configure:
cp ../.config .
${MAKE} olddefconfig
-   ${MAKE}
-
-# Only this target runs outside of fakeroot. We need to hook into it because
-# buildroot uses fakeroot itself.
-build: build-image
 
 # This target saves autotools outputs from output/. But we perform a clean
 # rebuild so that restoring the files may fail and is also not needed.
 override_dh_update_autotools_config:
 
-# We are building via build-image.
-override_dh_auto_build:
-
 # No test desired.
 override_dh_auto_test:
 
diff --git 
a/recipes-jailhouse/jailhouse/files/0001-arm-Fix-build-with-gcc-8.patch 
b/recipes-jailhouse/jailhouse/files/0001-arm-Fix-build-with-gcc-8.patch
new file mode 100644
index 000..ade9989
--- /dev/null
+++ b/recipes-jailhouse/jailhouse/files/0001-arm-Fix-build-with-gcc-8.patch
@@ -0,0 +1,56 @@
+From 9f233898917f8c1141132606f2f2c624405d8c81 Mon Sep 17 00:00:00 2001
+From: Jan Kiszka 
+Date: Sat, 13 Jul 2019 12:08:40 +0200
+Subject: [PATCH] arm: Fix build with gcc-8
+
+The inline .arch_extension statements are ignored by gcc-8. We rather
+need -march=armv7ve now.
+
+To keep older gcc prior to version 5 happy, leave the inline statements
+in place. Can be removed once we require newer gcc for other reasons.
+
+Reported-by: Vitaly Andrianov 
+Signed-off-by: Jan Kiszka 
+---
+ hypervisor/arch/arm/Makefile  | 2 +-
+ hypervisor/arch/arm/include/asm/smc.h | 1 +
+ hypervisor/arch/arm/include/asm/sysregs.h | 1 +
+ 3 files changed, 3 insertions(+), 1 deletion(-)
+
+diff --git a/hypervisor/arch/arm/Makefile b/hypervisor/arch/arm/Makefile
+index 2f930cf3..a170b593 100644
+--- a/hypervisor/arch/arm/Makefile
 b/hypervisor/arch/arm/Makefile
+@@ -12,4 +12,4 @@
+ 
+ LINUXINCLUDE += -I$(src)/arch/arm-common/include
+

[jh-images][PATCH 03/13] u-boot-ultra96: Update to 2019.07 and ATF 2.1

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

U-Boot requires an additional patch for the cross-building its tools.
ATF can drop the previously used compilation fix but needs a new one for
the ZynqMP specifically.

While at it, use the template mechanism for completing ultra96.bif.

Signed-off-by: Jan Kiszka 
---
 .../arm-trusted-firmware_2.1.inc   | 18 ++
 ...t-xilinx-zynqmp-Initialize-IPI-table-from.patch | 68 ++
 .../files/0001-zynqmp-Downgrade-to-PMUFW-0.3.patch | 12 ++--
 ...s-Makefile-fix-HOSTCFLAGS-with-CROSS_BUIL.patch | 31 ++
 .../u-boot/files/{ultra96.bif => ultra96.bif.tmpl} |  2 +-
 ...-atf1.6.bb => u-boot-ultra96_2019.07-atf2.1.bb} | 10 ++--
 6 files changed, 130 insertions(+), 11 deletions(-)
 create mode 100644 
recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.inc
 create mode 100644 
recipes-bsp/arm-trusted-firmware/files/0001-plat-xilinx-zynqmp-Initialize-IPI-table-from.patch
 create mode 100644 
recipes-bsp/u-boot/files/0002-Revert-tools-Makefile-fix-HOSTCFLAGS-with-CROSS_BUIL.patch
 rename recipes-bsp/u-boot/files/{ultra96.bif => ultra96.bif.tmpl} (87%)
 rename recipes-bsp/u-boot/{u-boot-ultra96_2019.01-atf1.6.bb => 
u-boot-ultra96_2019.07-atf2.1.bb} (86%)

diff --git a/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.inc 
b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.inc
new file mode 100644
index 000..8fd5cce
--- /dev/null
+++ b/recipes-bsp/arm-trusted-firmware/arm-trusted-firmware_2.1.inc
@@ -0,0 +1,18 @@
+#
+# Jailhouse, a Linux-based partitioning hypervisor
+#
+# Copyright (c) Siemens AG, 2019
+#
+# Authors:
+#  Jan Kiszka 
+#
+# SPDX-License-Identifier: MIT
+#
+
+FILESPATH =. "${LAYERDIR_jailhouse}/recipes-bsp/arm-trusted-firmware/files:"
+
+SRC_URI += " \
+
https://github.com/ARM-software/arm-trusted-firmware/archive/v${ATF_PV}.tar.gz;name=atf
 \
+
file://0001-plat-xilinx-zynqmp-Initialize-IPI-table-from.patch;patchdir=${WORKDIR}/arm-trusted-firmware-${ATF_PV}
 \
+"
+SRC_URI[atf.sha256sum] = 
"7c4c00a4f28d3cfbb235fd1a1fb28c4d2fc1d657c9301686e7d8824ef575d059"
diff --git 
a/recipes-bsp/arm-trusted-firmware/files/0001-plat-xilinx-zynqmp-Initialize-IPI-table-from.patch
 
b/recipes-bsp/arm-trusted-firmware/files/0001-plat-xilinx-zynqmp-Initialize-IPI-table-from.patch
new file mode 100644
index 000..dec3cb2
--- /dev/null
+++ 
b/recipes-bsp/arm-trusted-firmware/files/0001-plat-xilinx-zynqmp-Initialize-IPI-table-from.patch
@@ -0,0 +1,68 @@
+From f20643624a65cc8a992cbafe245af11fcf63ab6d Mon Sep 17 00:00:00 2001
+From: Jolly Shah 
+Date: Tue, 27 Aug 2019 11:23:08 -0700
+Subject: [PATCH] plat: xilinx: zynqmp: Initialize IPI table from
+ zynqmp_config_setup()
+
+Common ipi_table needs to be initialized before using any
+IPI command (i.e send/receive). Move zynqmp ipi config table
+initialization from sip_svc_setup() to zynqmp_config_setup().
+
+Signed-off-by: Tejas Patel 
+Signed-off-by: Jolly Shah 
+---
+ plat/xilinx/zynqmp/aarch64/zynqmp_common.c | 6 +-
+ plat/xilinx/zynqmp/sip_svc_setup.c | 4 
+ 2 files changed, 5 insertions(+), 5 deletions(-)
+
+diff --git a/plat/xilinx/zynqmp/aarch64/zynqmp_common.c 
b/plat/xilinx/zynqmp/aarch64/zynqmp_common.c
+index 8ff6c43604..ab5d95d1e2 100644
+--- a/plat/xilinx/zynqmp/aarch64/zynqmp_common.c
 b/plat/xilinx/zynqmp/aarch64/zynqmp_common.c
+@@ -1,5 +1,5 @@
+ /*
+- * Copyright (c) 2013-2016, ARM Limited and Contributors. All rights reserved.
++ * Copyright (c) 2013-2019, ARM Limited and Contributors. All rights reserved.
+  *
+  * SPDX-License-Identifier: BSD-3-Clause
+  */
+@@ -11,6 +11,7 @@
+ #include 
+ #include 
+ #include 
++#include 
+ #include 
+ #include 
+ 
+@@ -325,6 +326,9 @@ unsigned int zynqmp_get_bootmode(void)
+ 
+ void zynqmp_config_setup(void)
+ {
++  /* Configure IPI data for ZynqMP */
++  zynqmp_ipi_config_table_init();
++
+   zynqmp_print_platform_name();
+   generic_delay_timer_init();
+ }
+diff --git a/plat/xilinx/zynqmp/sip_svc_setup.c 
b/plat/xilinx/zynqmp/sip_svc_setup.c
+index edb81f5c3b..9b182749cb 100644
+--- a/plat/xilinx/zynqmp/sip_svc_setup.c
 b/plat/xilinx/zynqmp/sip_svc_setup.c
+@@ -9,7 +9,6 @@
+ #include 
+ #include 
+ 
+-#include 
+ #include "ipi_mailbox_svc.h"
+ #include "pm_svc_main.h"
+ 
+@@ -41,9 +40,6 @@ DEFINE_SVC_UUID2(zynqmp_sip_uuid,
+  */
+ static int32_t sip_svc_setup(void)
+ {
+-  /* Configure IPI data for ZynqMP */
+-  zynqmp_ipi_config_table_init();
+-
+   /* PM implementation as SiP Service */
+   pm_setup();
+ 
diff --git a/recipes-bsp/u-boot/files/0001-zynqmp-Downgrade-to-PMUFW-0.3.patch 
b/recipes-bsp/u-boot/files/0001-zynqmp-Downgrade-to-PMUFW-0.3.patch
index ce262b6..efc0bb8 100644
--- a/recipes-bsp/u-boot/files/0001-zynqmp-Downgrade-to-PMUFW-0.3.patch
+++ b/recipes-bsp/u-boot/files/0001-zynqmp-Downgrade-to-PMUFW-0.3.patch
@@ -1,7 +1,7 @@
-From 4a8103341c5420a65b80e9bbe0702bb66260b283 Mon Sep 17 00:00:00 2001
+From 1c7b8a169b9c10760debb6f35399fb2a59c3e250 Mon Sep 17

[jh-images][PATCH 09/13] non-root-initramfs: Autogenerate changelog

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

Signed-off-by: Jan Kiszka 
---
 recipes-core/non-root-initramfs/files/debian/changelog  | 5 -
 recipes-core/non-root-initramfs/non-root-initramfs_2019.02.2.bb | 2 +-
 2 files changed, 1 insertion(+), 6 deletions(-)
 delete mode 100644 recipes-core/non-root-initramfs/files/debian/changelog

diff --git a/recipes-core/non-root-initramfs/files/debian/changelog 
b/recipes-core/non-root-initramfs/files/debian/changelog
deleted file mode 100644
index 56f5b24..000
--- a/recipes-core/non-root-initramfs/files/debian/changelog
+++ /dev/null
@@ -1,5 +0,0 @@
-non-root-initramfs (@PV@) unstable; urgency=low
-
-  * Generated package.
-
- -- Jan Kiszka   Sat, 17 Feb 2018 00:00:00 +
diff --git a/recipes-core/non-root-initramfs/non-root-initramfs_2019.02.2.bb 
b/recipes-core/non-root-initramfs/non-root-initramfs_2019.02.2.bb
index 5ae36e0..1e642ee 100644
--- a/recipes-core/non-root-initramfs/non-root-initramfs_2019.02.2.bb
+++ b/recipes-core/non-root-initramfs/non-root-initramfs_2019.02.2.bb
@@ -26,7 +26,7 @@ do_prepare_build() {
cd ${WORKDIR}
 
cp -r debian ${S}
-   sed -i 's/@PV@/${PV}/' ${S}/debian/changelog
+   deb_add_changelog
 
ln -sf ${DISTRO_ARCH}-config .config
 }
-- 
2.16.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/39fad7fcfcada44861339d585d44b31c738af82a.1567490365.git.jan.kiszka%40siemens.com.

[jh-images][PATCH 11/13] demo-image: Add dbus package

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

WPA supplicant is looking for this. It worked nevertheless but gave an
ugly error during boot.

Signed-off-by: Jan Kiszka 
---
 recipes-core/images/demo-image.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/recipes-core/images/demo-image.bb 
b/recipes-core/images/demo-image.bb
index 2cd09e0..446f103 100644
--- a/recipes-core/images/demo-image.bb
+++ b/recipes-core/images/demo-image.bb
@@ -17,7 +17,7 @@ DESCRIPTION = "Jailhouse demo image (${MACHINE})"
 IMAGE_PREINSTALL += " \
 bash-completion less vim nano man \
 ifupdown isc-dhcp-client net-tools iputils-ping ssh \
-iw wireless-tools wpasupplicant \
+iw wireless-tools wpasupplicant dbus \
 pciutils usbutils ethtool iperf3"
 
 IMAGE_INSTALL += "jailhouse-${KERNEL_NAME}"
-- 
2.16.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/29dfbcf9ce31e7d3992128fcbcd3f48b0aa1976c.1567490365.git.jan.kiszka%40siemens.com.

[jh-images][PATCH 10/13] Update Isar revision

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

This moves to latest next, specifically pulling in the machine-id fix
that resolves boot-up delays.

Signed-off-by: Jan Kiszka 
---
 kas.yml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/kas.yml b/kas.yml
index 4ccba88..bbc7e69 100644
--- a/kas.yml
+++ b/kas.yml
@@ -21,7 +21,7 @@ repos:
 
   isar:
 url: https://github.com/ilbers/isar
-refspec: bdf8d29eacfde381e4e17a9b953328723cd9bea0
+refspec: 446783f6bc4bc3e96c31da93b5389e391e74d533
 layers:
   meta:
 
-- 
2.16.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/a65f8e9dc7331f7b58faf99fea5a13a40ca74028.1567490365.git.jan.kiszka%40siemens.com.

Re: Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Henning Schild 
A good way of estimating the cost of someone messing with ones caches
is to flush them yourself in your test and see how much that costs you.

I am not sure how complicated it is to read performance counters on
ARM, but those might give a clue.

AMBA QoS can maybe help raise the IO prio of your RT-cell. If a DMA
request is what is slowing down your GPIO.
I have never used that but maybe you can configure it from Linux before
you enable Jailhouse, and make sure that your root cell config blocks
future access to the configuration mechanism.

Henning



Am Mon, 2 Sep 2019 17:27:47 +0200
schrieb Ralf Ramsauer :

> Hi,
> 
> On 9/2/19 5:11 PM, Nir Geller wrote:
> > CPUFREQ is set to performance, and I'm setting scaling_min_freq to
> > the highest available frequency (150)
> > CPU idling is disabled
> > 
> > Now I see that executing a simple "cat somefile" on the command line
> > causes a spike in jitter  
> 
> only for the first time or also for consecutive calls on the same
> file? IOW, can you observe/trigger the spike when somefile is in your
> page cache?
> 
> Does the non-root cell share any devices with the root cell? (e.g.
> debug UART)
> 
>   Ralf
> 
> > 
> > On Monday, September 2, 2019 at 5:51:24 PM UTC+3, Henning Schild
> > wrote:
> > 
> > Am Mon, 2 Sep 2019 06:12:00 -0700
> > schrieb Nir Geller >:
> >   
> > > I created a kernel module that catches/releases a spinlock and
> > > disables/enables preemption, and it had no observable effect
> > > on the jitter, however,
> > > the operations insmod and rmmod definitely cause spikes in
> > > jitter.
> > >
> > > Any pointers?  
> > 
> > Do you have any power management features enabled in that Linux?
> > 
> > Henning
> >   
> > > Thanks.
> > >  
> > 
> > -- 
> > You received this message because you are subscribed to the Google
> > Groups "Jailhouse" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to jailhouse-dev+unsubscr...@googlegroups.com
> > .
> > To view this discussion on the web visit
> > https://groups.google.com/d/msgid/jailhouse-dev/a3c23a6a-95ee-4baa-9714-229c84d9d5b7%40googlegroups.com
> > .
> >   
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/20190902185713.0c54ed6b%40md1za8fc.ad001.siemens.net.

Re: Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Ralf Ramsauer 
Hi,

On 9/2/19 5:11 PM, Nir Geller wrote:
> CPUFREQ is set to performance, and I'm setting scaling_min_freq to the
> highest available frequency (150)
> CPU idling is disabled
> 
> Now I see that executing a simple "cat somefile" on the command line
> causes a spike in jitter

only for the first time or also for consecutive calls on the same file?
IOW, can you observe/trigger the spike when somefile is in your page cache?

Does the non-root cell share any devices with the root cell? (e.g. debug
UART)

  Ralf

> 
> On Monday, September 2, 2019 at 5:51:24 PM UTC+3, Henning Schild wrote:
> 
> Am Mon, 2 Sep 2019 06:12:00 -0700
> schrieb Nir Geller >:
> 
> > I created a kernel module that catches/releases a spinlock and
> > disables/enables preemption, and it had no observable effect on the
> > jitter, however,
> > the operations insmod and rmmod definitely cause spikes in jitter.
> >
> > Any pointers?
> 
> Do you have any power management features enabled in that Linux?
> 
> Henning
> 
> > Thanks.
> >
> 
> -- 
> You received this message because you are subscribed to the Google
> Groups "Jailhouse" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to jailhouse-dev+unsubscr...@googlegroups.com
> .
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/jailhouse-dev/a3c23a6a-95ee-4baa-9714-229c84d9d5b7%40googlegroups.com
> .

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/53ebbcfc-be0b-ab8d-5cd2-477e01d1dafc%40oth-regensburg.de.

Re: Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Nir Geller 
CPUFREQ is set to performance, and I'm setting scaling_min_freq to the 
highest available frequency (150)
CPU idling is disabled

Now I see that executing a simple "cat somefile" on the command line causes 
a spike in jitter

On Monday, September 2, 2019 at 5:51:24 PM UTC+3, Henning Schild wrote:
>
> Am Mon, 2 Sep 2019 06:12:00 -0700 
> schrieb Nir Geller >: 
>
> > I created a kernel module that catches/releases a spinlock and 
> > disables/enables preemption, and it had no observable effect on the 
> > jitter, however, 
> > the operations insmod and rmmod definitely cause spikes in jitter. 
> > 
> > Any pointers? 
>
> Do you have any power management features enabled in that Linux? 
>
> Henning 
>
> > Thanks. 
> > 
>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/a3c23a6a-95ee-4baa-9714-229c84d9d5b7%40googlegroups.com.

Re: Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Henning Schild 
Am Mon, 2 Sep 2019 06:12:00 -0700
schrieb Nir Geller :

> I created a kernel module that catches/releases a spinlock and 
> disables/enables preemption, and it had no observable effect on the
> jitter, however,
> the operations insmod and rmmod definitely cause spikes in jitter.
> 
> Any pointers?

Do you have any power management features enabled in that Linux?

Henning

> Thanks.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/20190902165120.7cc1048b%40md1za8fc.ad001.siemens.net.

Re: Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Nir Geller 
I created a kernel module that catches/releases a spinlock and 
disables/enables preemption, and it had no observable effect on the jitter, 
however,
the operations insmod and rmmod definitely cause spikes in jitter.

Any pointers?

Thanks.

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/bce2e24b-2063-4ce1-a1c9-c99efcd2ba5d%40googlegroups.com.

Interrupt Latency in RTOS inmate cell

2019-09-02 Thread Nir Geller 
Hi there,

I'm using Jailhouse 0.7 on a AM5728 based custom board, on which I'm 
running Linux on A15 core0 and TI-RTOS on A15 core1.
Linux kernel is 4.14.79 with RT-PREEMPT patch, supplied by TI.

On the TI-RTOS side I have an interrupt driven by a togglled GPIO at duty 
cycle of 31.25 usec, and I'm experiencing jitter of up to 40 usec.
This happens when both Linux and RTOS are not under any load.

When running the TI-RTOS natively on A15 core0 the jitter is stable and 
doesn't get higher than 12 usec, which is acceptable.

Also, I started the hypervisor and the TI-RTOS app, then I made the 
hypervisor park core0 by attempting to read a memory address that Linux is 
not allowed to access
and again on core1 the jitter is stable and doesn't get higher than 12 usec.

I guess that Linux is causing the interference.

Does Linux postpone/disable interrupts on core 1? Can it be avoided?
What else might cause the jitter?

Does it make sense to port Jailhouse to a newer version?

Thanks,

Nir.

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/361d6548-e251-4e1e-a03b-cdcbfda1b67d%40googlegroups.com.

Re: [PATCH v2] ci: Update build environment to Ubuntu 18.04

2019-09-02 Thread Jan Kiszka 

On 02.09.19 10:09, Jan Kiszka wrote:

From: Jan Kiszka 

This allows to switch to gcc 8 which may report issues earlier.

Powerpc does not build with gcc 8 and even also 7, so go with 6.

Signed-off-by: Jan Kiszka 
---

Changes in v2:
  - switch back to gcc 6
  - switch to gcc 8 for the rest

Steven, any chance we get ppc to a newer gcc? Are the issues

https://travis-ci.com/xenomai-ci/xenomai/jobs/229976797#L786
https://travis-ci.com/xenomai-ci/xenomai/jobs/229922504#L3071

fixed in newer 4.14 releases?

  .travis.yml | 15 +++
  1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 671c551f72..15efb7ccb1 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,15 +1,16 @@
  language: c
-dist: xenial
+dist: bionic
  cache: ccache
  
  addons:

apt:
  packages:
-  - gcc-aarch64-linux-gnu
+  - gcc-8
+  - gcc-8-aarch64-linux-gnu
- libc6-dev-arm64-cross
-  - gcc-arm-linux-gnueabihf
+  - gcc-8-arm-linux-gnueabihf
- libc6-dev-armhf-cross
-  - gcc-powerpc-linux-gnu
+  - gcc-6-powerpc-linux-gnu
- libc6-dev-powerpc-cross
- u-boot-tools
  
@@ -20,6 +21,10 @@ env:

  - CCACHE_MAXSIZE=400M
  
  install:

+  - sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800
+  - sudo update-alternatives --install /usr/bin/aarch64-linux-gnu-gcc 
aarch64-linux-gnu-gcc /usr/bin/aarch64-linux-gnu-gcc-8 800
+  - sudo update-alternatives --install /usr/bin/arm-linux-gnueabihf-gcc 
arm-linux-gnueabihf-gcc /usr/bin/arm-linux-gnueabihf-gcc-8 800
+  - sudo update-alternatives --install /usr/bin/powerpc-linux-gnu-gcc 
powerpc-linux-gnu-gcc /usr/bin/powerpc-linux-gnu-gcc-6 800
- git clone --depth 1 --branch ${IPIPE_REV} ${IPIPE_KERNEL} ${KDIR}
  
  before_script:

@@ -46,6 +51,8 @@ before_script:
- ln -s /usr/bin/ccache ~/ccache/arm-linux-gnueabihf-gcc
- ln -s /usr/bin/ccache ~/ccache/powerpc-linux-gnu-gcc
- export PATH=~/ccache:$PATH
+  - ${CROSS_COMPILE}gcc --version
+
- pushd ${KDIR}
- make -j $(nproc) ${KERNEL_DEFCONFIG}
  



Argh, wrong list, ignore.

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux

--
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/38ca40f7-fcde-ceaa-1c91-f4b809a9e0a6%40siemens.com.

[PATCH v2] ci: Update build environment to Ubuntu 18.04

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

This allows to switch to gcc 8 which may report issues earlier.

Powerpc does not build with gcc 8 and even also 7, so go with 6.

Signed-off-by: Jan Kiszka 
---

Changes in v2:
 - switch back to gcc 6
 - switch to gcc 8 for the rest

Steven, any chance we get ppc to a newer gcc? Are the issues

https://travis-ci.com/xenomai-ci/xenomai/jobs/229976797#L786
https://travis-ci.com/xenomai-ci/xenomai/jobs/229922504#L3071

fixed in newer 4.14 releases?

 .travis.yml | 15 +++
 1 file changed, 11 insertions(+), 4 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 671c551f72..15efb7ccb1 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -1,15 +1,16 @@
 language: c
-dist: xenial
+dist: bionic
 cache: ccache
 
 addons:
   apt:
 packages:
-  - gcc-aarch64-linux-gnu
+  - gcc-8
+  - gcc-8-aarch64-linux-gnu
   - libc6-dev-arm64-cross
-  - gcc-arm-linux-gnueabihf
+  - gcc-8-arm-linux-gnueabihf
   - libc6-dev-armhf-cross
-  - gcc-powerpc-linux-gnu
+  - gcc-6-powerpc-linux-gnu
   - libc6-dev-powerpc-cross
   - u-boot-tools
 
@@ -20,6 +21,10 @@ env:
 - CCACHE_MAXSIZE=400M
 
 install:
+  - sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800
+  - sudo update-alternatives --install /usr/bin/aarch64-linux-gnu-gcc 
aarch64-linux-gnu-gcc /usr/bin/aarch64-linux-gnu-gcc-8 800
+  - sudo update-alternatives --install /usr/bin/arm-linux-gnueabihf-gcc 
arm-linux-gnueabihf-gcc /usr/bin/arm-linux-gnueabihf-gcc-8 800
+  - sudo update-alternatives --install /usr/bin/powerpc-linux-gnu-gcc 
powerpc-linux-gnu-gcc /usr/bin/powerpc-linux-gnu-gcc-6 800
   - git clone --depth 1 --branch ${IPIPE_REV} ${IPIPE_KERNEL} ${KDIR}
 
 before_script:
@@ -46,6 +51,8 @@ before_script:
   - ln -s /usr/bin/ccache ~/ccache/arm-linux-gnueabihf-gcc
   - ln -s /usr/bin/ccache ~/ccache/powerpc-linux-gnu-gcc
   - export PATH=~/ccache:$PATH
+  - ${CROSS_COMPILE}gcc --version
+
   - pushd ${KDIR}
   - make -j $(nproc) ${KERNEL_DEFCONFIG}
 
-- 
2.16.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/08337573-b545-aff2-315b-174504c4caf2%40siemens.com.

[PATCH v2] ci: Update build environment to Ubuntu 18.04

2019-09-02 Thread Jan Kiszka 
From: Jan Kiszka 

This allows to switch to gcc 8 which may report issues earlier.

Signed-off-by: Jan Kiszka 
---

Changes in v2:
 - use gcc 8 rather than the default 7

 .travis.yml | 10 +++---
 1 file changed, 7 insertions(+), 3 deletions(-)

diff --git a/.travis.yml b/.travis.yml
index 8280912d..2d120561 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -11,7 +11,7 @@
 #
 
 language: c
-dist: xenial
+dist: bionic
 
 compiler:
   - gcc
@@ -20,9 +20,10 @@ addons:
   apt:
 packages:
   - python-mako
-  - gcc-arm-linux-gnueabihf
+  - gcc-8
+  - gcc-8-arm-linux-gnueabihf
   - libc6-dev-armhf-cross
-  - gcc-aarch64-linux-gnu
+  - gcc-8-aarch64-linux-gnu
   - libc6-dev-arm64-cross
   coverity_scan:
 project:
@@ -34,6 +35,9 @@ addons:
 branch_pattern: coverity_scan.*
 
 install:
+  - sudo update-alternatives --install /usr/bin/gcc gcc /usr/bin/gcc-8 800
+  - sudo update-alternatives --install /usr/bin/aarch64-linux-gnu-gcc 
aarch64-linux-gnu-gcc /usr/bin/aarch64-linux-gnu-gcc-8 800
+  - sudo update-alternatives --install /usr/bin/arm-linux-gnueabihf-gcc 
arm-linux-gnueabihf-gcc /usr/bin/arm-linux-gnueabihf-gcc-8 800
   # Work around broken certificate of scan.coverity.com
   - sudo curl -s -L https://entrust.com/root-certificates/entrust_l1k.cer -o 
/usr/local/share/ca-certificates/entrust_l1k.crt
   - sudo update-ca-certificates
-- 

2.16.4

-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/57ccfd93-38c8-e58a-5c28-c9b7b5fface0%40siemens.com.

[siemens/jailhouse] 955a94: ci: Update build environment to Ubuntu 18.04

2019-09-02 Thread Jan Kiszka 
  Branch: refs/heads/next
  Home:   https://github.com/siemens/jailhouse
  Commit: 955a9418df6edd88cf0f4496b029312df0bd7511
  
https://github.com/siemens/jailhouse/commit/955a9418df6edd88cf0f4496b029312df0bd7511
  Author: Jan Kiszka 
  Date:   2019-09-02 (Mon, 02 Sep 2019)

  Changed paths:
M .travis.yml

  Log Message:
  ---
  ci: Update build environment to Ubuntu 18.04

This allows to switch to gcc 8 which may report issues earlier.

Signed-off-by: Jan Kiszka 


-- 
You received this message because you are subscribed to the Google Groups 
"Jailhouse" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jailhouse-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jailhouse-dev/siemens/jailhouse/push/refs/heads/next/ed7c7c-955a94%40github.com.