Re: [PATCH v7 2/5] of: change overlay apply input data from unflattened to FDT

On Wed, Apr 4, 2018 at 5:35 PM, Jan Kiszka wrote: > Hi Frank, > > On 2018-03-04 01:17, frowand.l...@gmail.com wrote: >> From: Frank Rowand >> >> Move duplicating and unflattening of an overlay flattened devicetree >> (FDT) into the overlay application

Re: [PATCH v7 2/5] of: change overlay apply input data from unflattened to FDT

Hi Frank, On 2018-03-04 01:17, frowand.l...@gmail.com wrote: > From: Frank Rowand > > Move duplicating and unflattening of an overlay flattened devicetree > (FDT) into the overlay application code. To accomplish this, > of_overlay_apply() is replaced by

Re: [PATCH] arm: Initialize hrtimer-based broadcast clockevent

On 2018-03-01 07:04, Jan Kiszka wrote: > On 2018-01-22 07:06, Jan Kiszka wrote: >> Analogously to 9358d755bd5c, this registers a broadcast clockevent in >> case no hardware broadcast timer is available and the per-CPU timers can >> be stopped in deep power states. >> >> Partitions of the Jailhouse

[jh-images][PATCH 5/8] Update Isar, switching to new kernel/initrd deployment file names

From: Jan Kiszka This helps to select the right kernel and initrd image files, depending on the target. We need to update Isar in order to get the new naming scheme from upstream. Signed-off-by: Jan Kiszka --- kas.yml | 2 +- start-qemu.sh

[jh-images][PATCH 6/8] jailhouse: Add config file

From: Jan Kiszka Empty for amd64, but we will need it for other targets. Signed-off-by: Jan Kiszka --- recipes-jailhouse/jailhouse/files/qemuamd64_config.h | 1 + recipes-jailhouse/jailhouse/jailhouse.inc| 4 +++- 2 files changed, 4

[jh-images][PATCH 7/8] jailhouse: Prevent leaking CFLAGS and LDFLAGS from Debian environment

From: Jan Kiszka These flags should only be defined by our rules and the kernel. Not critical for x86, but other archs will expose this issue. See also linux-module recipe in Isar. Signed-off-by: Jan Kiszka ---

[jh-images][PATCH 1/8] linux: Update to 4.14.32

From: Jan Kiszka Just a stable update, no Jailhouse-related changes. Signed-off-by: Jan Kiszka --- recipes-kernel/linux/files/x86_64_defconfig | 2 +- recipes-kernel/linux/linux-jailhouse.bb | 6 +++--- 2 files changed, 4 insertions(+), 4

[jh-images][PATCH 8/8] customizations: Mark e1000e interface as hotplug

From: Jan Kiszka Makes it optional which will be relevant for targets with different interfaces. Signed-off-by: Jan Kiszka --- recipes-core/customizations/files/e1000e | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git

[jh-images][PATCH 0/8] Preparations for additional targets

Not yet the support for QEMU ARM64 - basically just waiting for proper cross-build support in Isar -, but this lays the ground for it by arranging configs and other artifacts so that adding another target will be straightforward. This also updates the kernel minor version. Jan CC: Jan Kiszka

[jh-images][PATCH 4/8] start-qemu: Move "-serial vc" into x86 section

From: Jan Kiszka Whether we have a second serial port is target-specific. Signed-off-by: Jan Kiszka --- start-qemu.sh | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/start-qemu.sh b/start-qemu.sh index 07f891a..33b5cd7

[jh-images][PATCH 3/8] linux-jailhouse: Select defconfig via MACHINE name

From: Jan Kiszka This makes it easier to add further targets with their own defconfigs. Signed-off-by: Jan Kiszka --- recipes-kernel/linux/files/{x86_64_defconfig => qemuamd64_defconfig} | 0 recipes-kernel/linux/linux-jailhouse.bb

Re: Share memory among cells on arm64

Hi, what you see there are the registers of the ivshmem device, not the payload memory region. You will have to map the paddr you have in your cell-config. That paddr can be found in the config space as well, is just not a regular PCI BAR. I would suggest to write a uio driver and base it on