Compilation and virtualization in the HiPEAC vision

Abstract

This paper describes the HiPEAC vision of embedded virtualization as it has developed during two years of discussion among the members of the HiPEAC cluster on binary translation and virtualization. We start from system virtualization and process virtualization and we gradually develop a vision in which the two merge into one virtualization layer for embedded systems. Such a unified virtualization offers solutions for consolidation, performance optimization, software engineering and dealing with legacy hardware components. Four adoption requirements are identified: support for real-time execution, low performance overhead, virtualization of accelerator cores and finally trustworthiness. Finally, we define four research challenges: full virtualization of heterogeneous multi-core platforms, portable performance for heterogeneous multi-cores, virtual machine management interfaces, and standards for embedded virtualization

Current techniques and future trends in embedded system's virtualization

“…Although paravirtualization is a very common way of allowing virtualization for both embedded and non‐ESs, its efficient implementation is too time consuming. Adapting an OS is not a trivial task, especially if the OS was not written by the part trying to virtualize it by adjusting to a given hypervisor ; Virtual machine management must be as easy, simple, and straightforward as possible. In mobile phones and future pervasive devices, virtualization can enable many functions that are not possible currently, especially because of security purposes; Lightweight hypervisors for nonrobust embedded processors.…”

Hardware-assisted virtualization targeting MIPS-based SoCs

“…We are using a mixed approach that combines full virtualization and native execution, as this appears to be a valid and ideal approach for embedded systems [13]. We are aware of the challenges since the emulation's overhead can become prohibitive, but we believe that appropriate hardware support must fill that gap.…”

“…Therefore, our solution contemplates implementation strategies to soften the implicit overhead of non-paravirtualized solutions as will be shown throughout this paper. As pointed in [13] and in [3], the use of architectural support to enable full virtualization is already a reality also for embedded systems 1 as one of the most used architectures, ARM, has already had its own architectural support announced [14].…”

Predictable Binary Code Cache: A First Step towards Reconciling Predictability and Just-in-Time Compilation

“…One way to address this heterogeneity is the introduction of virtualization [2]. Programs are no longer compiled to native code, but rather target a platform-neutral bytecode representation.…”