Xen on ARM is becoming more and more widespread in embedded environments. In these contexts, Xen is employed as a single solution to partition the system into multiple domains, fully isolated from each other, and with different levels of trust. Every embedded scenario is different, but many require real-time guarantees.
We just wrapped another successful Xen Project Hackathon, which is an annual event, hosted by Xen Project member companies, typically at their corporate offices. This year’s event was hosted by ARM at their Cambridge HQ. 42 delegates descended on Cambridge from Aporeto, ARM, Assured Information Security, Automotive Electrical Systems,
I am pleased to announce the next Xen Project Hackathon. The Hackathon will be hosted by ARM in their Cambridge Headquarters from April 18 and 19. I wanted to thank Philippe Robin and Thomas Molgaard from ARM for hosting the Hackathon. ARM designs technology that is at the heart of
One of the challenges of using Xen in embedded environments is the need for core components to meet critical timing requirements. In traditional implementations engineers use real-time operating systems (RTOS) to ensure, for example, that an automobile’s brakes engage within a reasonable amount of time after the driver presses
OK, maybe the title of this post is a slight exaggeration but it’s good to have goals for the future! It’s a goal which many would argue will be unreachable without the genesis of Strong AI. It’s also a goal where we can achieve very useful results