Difference between revisions of "Xen ARM TODO"

From Xen
(Removed fixed bgu)
Line 6: Line 6:
 
== Known Bugs ==
 
== Known Bugs ==
 
=== Versatile Express ===
 
=== Versatile Express ===
{{Open Bug
 
|Bug=linux v3.8-rc2 boot failed on versatile express
 
|Status=Fixed
 
|Desc=
 
Linux v3.8-rc2 fails to change the MMC voltage during boot on Versatile Express.
 
|References=[http://marc.info/?l=linux-kernel&m=135843574114719&w=2 patch] is needed to fix the bug.
 
}}
 
   
 
=== Arndale Board ===
 
=== Arndale Board ===
{{Open Bug
 
|Bug=Guest hang with multi-vcpu
 
|Status=Fixed
 
|Desc=Hangs on the Arndale board with multi-vcpu guests.
 
|References=[http://marc.info/?l=xen-devel&m=136510786507930 patch] is needed to fix the bug.
 
}}
 
{{Open Bug
 
|Bug=Network doesn't work in the guest
 
|Contact=julien.grall@citrix.com
 
|Status=In progress
 
|Desc=Network doesn't work in the guest when an ehternet cable is plugged
 
|References=http://pastebin.com/gEP3HdCg
 
}}
 
{{Open Bug
 
|Bug=Sometimes Guest can't extract the initramfs
 
|Status=Open
 
|Desc=When Xen tries to copy data from the guest, it fails to unmap some page because nobody(?) mapped it.
 
|References=http://pastebin.com/frbeiuxz
 
}}
 
 
   
 
== Open Work Items ==
 
== Open Work Items ==

Revision as of 14:02, 7 January 2014

This is a list of open work items and known bugs for the Xen on ARM with virtualization extension project.


In progress

Known Bugs

Versatile Express

Arndale Board

Open Work Items

vGIC interrupt prioritisation
Contact: xen-devel@lists.xen.org
Description: Currently the vGIC only implements a very basic form of interrupt priority, in particular it is not able to preempt an inflight lower priority interrupt when a new higher priority one occurs. The emulation needs to consider the vCPUs current IAR as well as the priorities of pending and inflight interrupts.
References: Not specified, useful references.

VCPU virtual time support
Contact: xen-devel@lists.xen.org
Description: Currently the concept of virtual time exposed to the guests is very simplistic and is just a static offset from physical time based on the time when the guest was started. We need to consider if this is actually what is needed/wanted and consider cases such as stolen time etc.
References: Not specified, useful references.

IOMMU support in Xen
Contact: xen-devel@lists.xen.org
Description: write a driver in Xen for the ARM System Memory Management Unit (SMMU), use it to assign devices to Dom0.
References: Not specified, useful references.

Save/restore and migration
Contact: xen-devel@lists.xen.org
Description: Make VM save/restore and VM migration work on ARM.
References: InProgress: http://lists.xen.org/archives/html/xen-devel/2013-10/msg00192.html

Use Superpage mappings for P2M
Contact: xen-devel@lists.xen.org
Description: Currently we use 4K pages everywhere. Xen should attempt to use 2MB mappings in the P2M wherever possible.

This will have significant performance benefits.

Need to do 2MB ballooning too.
References: Not specified, useful references.

Device assignment to DomUs
Contact: xen-devel@lists.xen.org
Description: Assign one or more devices to an unprivileged guest, re-program the SMMU accordingly.
References: Not specified, useful references.

Expose Wallclock time to guests
Contact: xen-devel@lists.xen.org
Description: Current Xen on ARM does not popular the wallclock time fields of the shared info with anything useful. It should do so...
References: Not specified, useful references.