Linaro Virtualization status 10 Apr 2013 (Weeks 13/14)
Linaro Virtualization Team's Weekly Report - Weeks 13/14 2013 = During the last 2 weeks (27 March - 10 April 2013) the team has been working on the following areas. More detailed information can be found on the meeting reports wiki page [0]. Ongoing work * BOOTLOADER HYP MODE SUPPORT FOR ARMv7 [1] by Andre Przywara * rebase existing Versatile Express patches against upstream u-boot [2] Done: - Reworked patch for Versatile Express to be more reusable for other boards. - U-Boot patch sent as RFC, waiting for reaction. * implement HYP command to let u-boot switch into HYP mode [3] Done: - HYP mode switch works reliably. - SMP is working too. - VExpress patches sent upstream (V3 of the patch set). - discovered a bug in Linux 3.9-rc: - DMA refactoring broke Versatile Express: NULL pointer exception. - Patches already are on ML, but not yet in HEAD (3.9rc5-77) - discovered related issue with DMA PL330 on Highbank (Rob@Calxeda seems to care about this) * ARMv7 KVM GUEST MIGRATION [4] by Peter Maydell and Andre Przywara * QEMU: audit the vexpress model for devices we use which do not currently have migration support [5] by Peter Maydell Done: - task completed. - patches now preliminarily queued in arm-devs.next, though if there is a late-breaking issue with one of them it will have to be fixed and patches updated. * QEMU: implement full cp15 sync with kernel [6] by Peter Maydell Done: - Some work that was assumed to be already committed last year appeared to be still pending - hew sub-task created: QEMU: move CPU migration to vmstate [7] Working on: - pending for [7] to complete. * QEMU: move CPU migration to vmstate [7] Done: - updated patches from Juan Quintela from last year which are updating the migration state for the CPU itself to use VMState structures. Working on: - testing and tweaking of the updated patches. * kernel: agree on a data structure to describe timer state [8] by Andre Przywara Working on: - reading documentation. - thinking about code structure. - timer migration prototype. * ARMv8 KVM QEMU prototype [9] * Add skeleton ARM64 build patches to local tree [10] Done: - completed this sub-task. * Add arm64 mach-virt system model skeleton [11] Working on: - only has serial, can add virtio stuff later. - in progress. * Add creating FDT from scratch to mach-virt system model [12] Working on: - in progress, nearly done. * Add kvm guest creation and launching of armv8/mach-virt [13] Working on: - in progress, just started. * IN KERNEL SUPPORT FOR KVM ARMv8 [14] by Anup Patel and Pranavkumar Sawargaonkar, Geoff Levand Done: - KVM ARMv8 patch set review, fixes suggested (by Geoff). - Initial patch set for APM board bring up is reviewed internally in APM and is queued for upstreaming in near future. - real AMRv8 hardware is accessible to Anup and Pranav - switched to it for further work. - ARMv8 kernel is bootable on the board now. - U-Boot is starting the kernel in HYP mode on the board now. Working on: - Debugging the guest part now (on the board). Currently it is not booting (still in early debug). - Hacky early printk support in kvmtool is to be properly submitted to the ML as an RFC. * CI BRING UP: KVM ARMv7 [15] by Riku Voipio Done: - Find out howto include guest image in host image. - Create ci.linaro.org jobs for submitting validation tests to LAVA for VE TC2. Working on: - Create ci.linaro.org jobs for submitting validation tests to LAVA for Arndale. Links - [0] https://wiki.linaro.org/LEG/Engineering/Virtualization/TeamMeetingReports [1] http://cards.linaro.org/browse/CARD-361 [2] http://cards.linaro.org/browse/VIRT-70 [3] http://cards.linaro.org/browse/VIRT-71 [4] http://cards.linaro.org/browse/CARD-363 [5] http://cards.linaro.org/browse/VIRT-51 [6] http://cards.linaro.org/browse/VIRT-49 [7] http://cards.linaro.org/browse/VIRT-73 [8] http://cards.linaro.org/browse/VIRT-42 [9] http://cards.linaro.org/browse/CARD-221 [10] http://cards.linaro.org/browse/VIRT-52 [11] http://cards.linaro.org/browse/VIRT-53 [12] http://cards.linaro.org/browse/VIRT-54 [13] http://cards.linaro.org/browse/VIRT-56 [14] htt
big.LITTLE MP Scheduler test summary-week-15
Hi, Release test report big.LITTLE MP week-15: Here is test result summary for big.LITTLE MP Scheduler test on TC2 platform with Android image sched_tests.git No of Test Cases Tests Run Tests Pass Tests Fail Absolute pass rate (%) Failure Analysis/Comments Regression 2019 19 0 100 % mpbasicsuite 1410 10 0 100 % mpcoresuite 10 65 1 90 % mpextendedsuite 20 10 6 460 % mploadbalance 2 22 0 100 % Android Build: https://android-build.linaro.org/builds/~linaro-android/vexpress-linaro-mp/#build=254 Linux kernel: Linux version 3.9.0-rc5-00238-g2b23d54 (jenkins-build@ip-10-226-9 7-251) (gcc version 4.7.3 20130226 (prerelease) (Linaro GCC 4.7-2013.03) ) #1 SMP Wed Apr 10 04:53:19 UTC 2013 Results spread sheet: https://docs.google.com/a/linaro.org/spreadsheet/ccc?key=0Ai9ggMs8bsGJdER3azBqWGtXNjRwb1UzSnZ4RGg3OUE#gid=15 Best regards Naresh Kamboju ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[PATCH] omap4.conf: Disable OMAP2 support
When the kernel is built with CONFIG_ARCH_OMAP2 it will select CPU_V6 and other dependencies which causes issues in user space. For example when clients try to connect to PulseAudio they will crash with: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. Remove support for OMAP2 for now. Signed-off-by: Peter Ujfalusi --- Hi Andrey, Can you take a look at this patch? In the latest hwpack for panda (with 3.9 kernel) PulseAudio clients all asserts with the following error: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. The same userspace works fine (well, mostly) with 3.8 based hwpacks. It turns out that this is cased by the CONFIG_ARCH_OMAP2, if we disable it PA clients no longer assert. Since the config in question is for OMAP4, I see no issue removing the OMAP2 support since in this way we can get PA working. One issue still remain with PA: None of float resample method works: speex-float-[0-10] However speex-fixed-[0-10] and ffmpeg seams to be working, but it is not perfect. I'll try to figure out why we have this failure since on my Gentoo FS all resample method works fine with the same kernel. Regards, Peter linaro/configs/omap4.conf |1 + 1 file changed, 1 insertion(+) diff --git a/linaro/configs/omap4.conf b/linaro/configs/omap4.conf index 59e9f23..82c9365 100644 --- a/linaro/configs/omap4.conf +++ b/linaro/configs/omap4.conf @@ -11,6 +11,7 @@ CONFIG_OMAP_RESET_CLOCKS=y CONFIG_OMAP_MUX_DEBUG=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_SOC_OMAP5=y +CONFIG_ARCH_OMAP2=n CONFIG_ARCH_VEXPRESS_CA9X4=y CONFIG_ARM_THUMBEE=y CONFIG_ARM_ERRATA_411920=y -- 1.7.10.4 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
[PATCH] omap4.conf: Disable OMAP2 support
When the kernel is built with CONFIG_ARCH_OMAP2 it will select CPU_V6 and other dependencies which causes issues in user space. For example when clients try to connect to PulseAudio they will crash with: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. Remove support for OMAP2 for now. Signed-off-by: Peter Ujfalusi --- Hi Andrey, Can you take a look at this patch? In the latest hwpack for panda (with 3.9 kernel) PulseAudio clients all asserts with the following error: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. The same userspace works fine (well, mostly) with 3.8 based hwpacks. It turns out that this is cased by the CONFIG_ARCH_OMAP2, if we disable it PA clients no longer assert. Since the config in question is for OMAP4, I see no issue removing the OMAP2 support since in this way we can get PA working. One issue still remain with PA: None of float resample method works: speex-float-[0-10] However speex-fixed-[0-10] and ffmpeg seams to be working, but it is not perfect. I'll try to figure out why we have this failure since on my Gentoo FS all resample method works fine with the same kernel. Regards, Peter linaro/configs/omap4.conf |1 + 1 file changed, 1 insertion(+) diff --git a/linaro/configs/omap4.conf b/linaro/configs/omap4.conf index 59e9f23..82c9365 100644 --- a/linaro/configs/omap4.conf +++ b/linaro/configs/omap4.conf @@ -11,6 +11,7 @@ CONFIG_OMAP_RESET_CLOCKS=y CONFIG_OMAP_MUX_DEBUG=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_SOC_OMAP5=y +CONFIG_ARCH_OMAP2=n CONFIG_ARCH_VEXPRESS_CA9X4=y CONFIG_ARM_THUMBEE=y CONFIG_ARM_ERRATA_411920=y -- 1.7.10.4 ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: [PATCH] omap4.conf: Disable OMAP2 support
On 04/12/2013 05:51 PM, Peter Ujfalusi wrote: When the kernel is built with CONFIG_ARCH_OMAP2 it will select CPU_V6 and other dependencies which causes issues in user space. For example when clients try to connect to PulseAudio they will crash with: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. Remove support for OMAP2 for now. Signed-off-by: Peter Ujfalusi --- Hi Andrey, Can you take a look at this patch? In the latest hwpack for panda (with 3.9 kernel) PulseAudio clients all asserts with the following error: Assertion 'pthread_mutex_unlock(&m->mutex) == 0' failed at pulsecore/mutex-posix.c:108, function pa_mutex_unlock(). Aborting. The same userspace works fine (well, mostly) with 3.8 based hwpacks. It turns out that this is cased by the CONFIG_ARCH_OMAP2, if we disable it PA clients no longer assert. Since the config in question is for OMAP4, I see no issue removing the OMAP2 That's right. The patch has been added to kernel/configs.git, config-boards-tracking and config-boards-3.9 branches, and included into linux-linaro, the ll-20130412.0 tag. Thanks, Andrey support since in this way we can get PA working. One issue still remain with PA: None of float resample method works: speex-float-[0-10] However speex-fixed-[0-10] and ffmpeg seams to be working, but it is not perfect. I'll try to figure out why we have this failure since on my Gentoo FS all resample method works fine with the same kernel. Regards, Peter linaro/configs/omap4.conf |1 + 1 file changed, 1 insertion(+) diff --git a/linaro/configs/omap4.conf b/linaro/configs/omap4.conf index 59e9f23..82c9365 100644 --- a/linaro/configs/omap4.conf +++ b/linaro/configs/omap4.conf @@ -11,6 +11,7 @@ CONFIG_OMAP_RESET_CLOCKS=y CONFIG_OMAP_MUX_DEBUG=y CONFIG_ARCH_OMAP2PLUS=y CONFIG_SOC_OMAP5=y +CONFIG_ARCH_OMAP2=n CONFIG_ARCH_VEXPRESS_CA9X4=y CONFIG_ARM_THUMBEE=y CONFIG_ARM_ERRATA_411920=y ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Mali-ization
Hi - At the moment the Mali T624 OOT module sources I have do not build against 3.9-rcX / linux-linaro-core-tracking. A colleague checked it and it does build against 3.4. The problems I saw are around ION compatibility but they didn't look tremendously bad. I could work around the problems myself, but it seems to me this might be something that Linaro could solve centrally, dealing with it using the Androidization model - sync a Linaro repo against code drops coming from "upstream", ie, ARM, but keep it always building against llct inbetween. Perhaps even inside llct. I know we're not the only LT in this boat, Anmar mentioned Arndale acceleration is pending, a central Mali-ization tree will also solve that, especially if it's always there and always building in llct already. There may be stuff to take care about for support for different IP revision. But there aren't that many AFAIK. How does this sound to folks? -Andy -- Andy Green | Fujitsu Landing Team Leader Linaro.org │ Open source software for ARM SoCs | Follow Linaro http://facebook.com/pages/Linaro/155974581091106 - http://twitter.com/#!/linaroorg - http://linaro.org/linaro-blog ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Mali-ization
On 04/12/2013 05:34 PM, Andy Green wrote: Hi - At the moment the Mali T624 OOT module sources I have do not build against 3.9-rcX / linux-linaro-core-tracking. A colleague checked it and it does build against 3.4. The problems I saw are around ION compatibility but they didn't look tremendously bad. Any details on what the ION compatibility issues are? I could work around the problems myself, but it seems to me this might be something that Linaro could solve centrally, dealing with it using the Androidization model - sync a Linaro repo against code drops coming from "upstream", ie, ARM, but keep it always building against llct inbetween. Perhaps even inside llct. The idea of having a mali-ization tree sounds like a reasonable approach. That said, if there are any patches against the ION code needed, I'd be interested in seeing them. Right now is a particularly good time for getting Android dependent patches into AOSP, as linux-linaro isn't very far from the latest AOSP branch, and we've had some good success here over the last week or so. thanks -john ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
Re: Mali-ization
On 13/04/13 08:50, the mail apparently from John Stultz included: On 04/12/2013 05:34 PM, Andy Green wrote: Hi - At the moment the Mali T624 OOT module sources I have do not build against 3.9-rcX / linux-linaro-core-tracking. A colleague checked it and it does build against 3.4. The problems I saw are around ION compatibility but they didn't look tremendously bad. Any details on what the ION compatibility issues are? Build with ION looks like this atm pwd=/projects/linaro/mali-t624/kernel/drivers/gpu/arm/t6xx/kbase make -C /projects/linaro/mali-t624/kernel/drivers/gpu/arm/t6xx/kbase/../../../../../../kernel/drivers/base/kds make[1]: Entering directory `/projects/linaro/mali-t624/kernel/drivers/base/kds' make ARCH=arm -C /projects/linaro/mali-t624/kernel/../../linux-2.6/panda M=/projects/linaro/mali-t624/kernel/drivers/base/kds EXTRA_CFLAGS="-I/projects/linaro/mali-t624/kernel/drivers/base/kds/../../../include" CONFIG_KDS=m make[2]: Entering directory `/projects/linaro/linux-2.6/panda' LD /projects/linaro/mali-t624/kernel/drivers/base/kds/built-in.o CC [M] /projects/linaro/mali-t624/kernel/drivers/base/kds/kds.o Building modules, stage 2. MODPOST 1 modules CC /projects/linaro/mali-t624/kernel/drivers/base/kds/kds.mod.o LD [M] /projects/linaro/mali-t624/kernel/drivers/base/kds/kds.ko make[2]: Leaving directory `/projects/linaro/linux-2.6/panda' make[1]: Leaving directory `/projects/linaro/mali-t624/kernel/drivers/base/kds' make -C /projects/linaro/mali-t624/kernel/drivers/gpu/arm/t6xx/kbase/../../../../../../kernel/drivers/base/ump/src make[1]: Entering directory `/projects/linaro/mali-t624/kernel/drivers/base/ump/src' make ARCH=arm -C /projects/linaro/mali-t624/kernel/../../linux-2.6/panda M=/projects/linaro/mali-t624/kernel/drivers/base/ump/src EXTRA_CFLAGS="-I/projects/linaro/mali-t624/kernel/drivers/base/ump/src/../../../../include -DCONFIG_UMP -DCONFIG_MALI_DEBUG -DCONFIG_MALI_PLATFORM_FAKE -DCONFIG_MALI_PLATFORM_VEXPRESS -DCONFIG_MALI_UNCACHED -DCONFIG_MALI_GATOR_SUPPORT -DCONFIG_KDS" CONFIG_UMP=m KBUILD_EXTRA_SYMBOLS=" /projects/linaro/mali-t624/kernel/drivers/base/ump/src/../../../../../kernel/drivers/base/kds/Module.symvers" modules make[2]: Entering directory `/projects/linaro/linux-2.6/panda' CC [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/common/ump_kernel_core.o CC [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/common/ump_kernel_descriptor_mapping.o CC [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/linux/ump_kernel_linux.o CC [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/linux/ump_kernel_linux_mem.o LD [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/ump.o CC [M] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.o /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c: In function ‘import_ion_client_create’: /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:52:2: warning: passing argument 2 of ‘ion_client_create’ makes pointer from integer without a cast [enabled by default] In file included from /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:17:0: /projects/linaro/linux-2.6/include/linux/ion.h:128:20: note: expected ‘const char *’ but argument is of type ‘unsigned int’ /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:52:2: error: too many arguments to function ‘ion_client_create’ In file included from /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:17:0: /projects/linaro/linux-2.6/include/linux/ion.h:128:20: note: declared here /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c: In function ‘import_ion_final_release_callback’: /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:79:2: error: implicit declaration of function ‘ion_unmap_dma’ [-Werror=implicit-function-declaration] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c: In function ‘import_ion_import’: /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:112:2: error: implicit declaration of function ‘ion_import_fd’ [-Werror=implicit-function-declaration] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:112:23: warning: assignment makes pointer from integer without a cast [enabled by default] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:119:2: error: implicit declaration of function ‘ion_map_dma’ [-Werror=implicit-function-declaration] /projects/linaro/mali-t624/kernel/drivers/base/ump/src/imports/ion/ump_kernel_import_ion.c:119:19: warning: assignment makes pointer from integer without a cast [enabled by
Question relating to arm
>From my research I gather arm is just an architecture or chip producer as well? As i have a project, that might do sufficiently running on a dev board, or even a custom developed arm based board. I have been trying to find a contact email at arm but to no avail. Any help and information would be greatly appreciated. -- Jonathan Aquilina ___ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
