Latest News
- Xvisor v0.3.2
Sun, 1 Jan 2023 18:39:42 +0530
- Xvisor v0.3.1
Mon, 20 Dec 2021 10:41:27 +0530
- Xvisor RISC-V talk at OSS and ELC Europe 2019
Thu, 2 Jan 2020 12:03:57 +0530
- Xvisor v0.3.0
Wed, 1 Jan 2020 12:08:37 +0530
- Xvisor talk at GENIVI Summit 2018
Mon, 22 Oct 2018 18:17:00 +0530
- Xvisor v0.2.11
Sun, 21 Oct 2018 09:49:38 +0530
- Supporting Temporal and Spatial Isolation in a Hypervisor for ARM Multicore Platforms
Tue, 10 Apr 2018 10:44:25 +0530
- Reconciling Security with Virtualization: A Dual-Hypervisor Design for ARM TrustZone
Tue, 10 Apr 2018 10:44:25 +0530
Upcoming Events
New Feature: Runtime loadable modules Date: Wed, 8 Aug 2012 11:47:48 +0530 | Posted by: Anup Patel
We have "Runtime Loadable Modules" support available in Xvisor. This will be available in mainline tree from next release.
To list all available modules use "module list" command.
To get detailed info about any module we can use "module info <index>"command.
To make module as loadable module:
- mark the module as "M" from menuconfig (Note: the openconf option for loadable module should be tristate and not bool)
- compile Xvisor "make"
- compile loadable modules "make modules"
To load a module (.xo object file) from any memory location using "module load <phys_addr> <phys_size>" command. For e.g.
XVisor# module load 0x70600000 0x10000(Note: In future, same "module load" command will support loading .xo objects stored in some storage device)
To unload a module we have to use "module unload
(Note: "built-in" modules cannot be unloaded. Only "loadable" modules can be unloaded.)
Xvisor is now fully extensible hypervisor and can be extended at compile-time as well as run-time.
This also opens doors for a wide variety of proprietary solutions (non-GPL) such as:
- Proprietary drivers
- Proprietary emulators
- Proprietary daemons
- Bla Bla Bla ....