Archived/Xen Development Projects: Difference between revisions

From Xen
Jump to navigationJump to search
No edit summary
No edit summary
Line 4: Line 4:
<!-- Page revision: 00000010 -->
<!-- Page revision: 00000010 -->
<!-- Original date: Thu Jan 6 13:04:51 2011 (1294319091000000) -->
<!-- Original date: Thu Jan 6 13:04:51 2011 (1294319091000000) -->

__NOTOC__
__NOTOC__
This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?
This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?
Line 20: Line 19:
Before to submit patches, please look at [[Submitting Xen Patches]] wiki page.
Before to submit patches, please look at [[Submitting Xen Patches]] wiki page.


If you have new ideas, suggestions or development plans let us know and we'll update this list!


== List of projects ==
== List of projects ==
If you have new ideas, suggestions or development plans let us know and we'll update this list!

=== Domain support ===
=== Domain support ===
{{project
{{project

Revision as of 13:48, 8 August 2012


This page lists various Xen related development projects that can be picked up by anyone! If you're interesting in hacking Xen this is the place to start! Ready for the challenge?

To work on a project:

  • Find a project that looks interesting.
  • Send an email to xen-devel mailinglist and let us know you started working on a specific project.
  • Post your ideas, questions, RFCs to xen-devel sooner than later so you can get comments and feedback.
  • Send patches to xen-devel early for review so you can get feedback and be sure you're going into correct direction.
  • Your work should be based on xen-unstable development tree, if it's Xen and/or tools related. After your patch has been merged to xen-unstable it can be backported to stable branches (Xen 4.0, Xen 3.4, etc).
  • Your kernel related patches should be based on either upstream kernel.org git tree (latest version), or xen/stable-2.6.32.x tree, depending if it's upstream or xen dom0 related work.

xen-devel mailinglist subscription and archives: http://lists.xensource.com/mailman/listinfo/xen-devel

Before to submit patches, please look at Submitting Xen Patches wiki page.

If you have new ideas, suggestions or development plans let us know and we'll update this list!

List of projects

Domain support

Upstreaming Xen PVSCSI drivers to mainline Linux kernel

Date of insert: 01/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: PVSCSI drivers needs to be upstreamed yet. Necessary operations may include:
Outcomes: Not specified, project outcomes


Upstreaming Xen PVUSB drivers to mainline Linux kernel

Date of insert: 01/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: PVUSB drivers needs to be upstreamed yet. Necessary operations may include:
Outcomes: Not specified, project outcomes


Blkback improvements

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Blkback requires a number of improvements, some of them being:
  • Multiple disks in a guest cause contention in the global pool of pages.
  • There is only one ring page and with SSDs nowadays we should make this larger, implementing some multi-page support.
  • With multi-page it becomes apparent that the segment size ends up wasting a bit of space on the ring. BSD folks fixed that by negotiating a new parameter to utilize the full size of the ring.
  • Add DIF/DIX support [1]
  • Further perf evaluation needs to be done to see how it behaves under high load.
Outcomes: Not specified, project outcomes


Netback overhaul

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Wei Liu posted RFC patches that make the driver be multi-page, multi-event channel and with a page-pool. However not all the issues have been addressed yet, meaning that the patches need to be finished and cleaned up yet. Additively, a zero-copy implementation can be considered. Patch serie and discussions:
Outcomes: Not specified, project outcomes


PAT writecombine fixup

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: The writecombine feature (especially for graphic adapters) is turned off due to stability reasons. More specifically, the code involved in page transition from WC to WB gets confused about the PSE bit state in the page, resulting in a set of repeated warnings.

For more informations please check:

Outcomes: Not specified, project outcomes


ACPI S3-state investigation and fixup

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: During Linux-3.3 release the the S3-state was supposed to work including these patches: But now it is not working anymore. Scope of the project is understanding the reasons for the issues and fix them.
Outcomes: Not specified, project outcomes


PUD L3 - big memory - fixup

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Right now guests don't boot with a huge amount of requested kernel memory (tries report failing with certainly 384GB). Scope of the project is understanding the reasons and fix them. This likely involves digging into the toolstack too.
Outcomes: Not specified, project outcomes


Parallel xenwatch

Date of insert: 01/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Xenwatch is locked with a coarse lock. For a huge number of guests this represents a scalability issue. The need is to rewrite the xenwatch locking in order to support full scalability.
Outcomes: Not specified, project outcomes

Hypervisor

Microcode uploader implementation

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Intel is working on early implementation where the microcode blob would be appended to the initrd image. The kernel would scan for the appropiate magic constant and load the microcode very early. The Xen hypervisor can do this similary.
Outcomes: Not specified, project outcomes


SEDF Handling of Blocking/Unblocking

Date of insert: 08/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Dario Faggioli <dario.faggioli@citrix.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: The SEDF scheduler, within Xen, currently deals with events such as a vcpu blocking (in general, stopping running) and unblocking (in general, restarting running) by trying (but failing!) to special case all the possible situations, resulting in the code being rather complicated, ugly, inefficient and hard to maintain. Unified approaches have been proposed for enabling blocking and unblocking in EDF (the algorithm the scheduler uses), without compromising the temporal isolation it provides to the various tasks/vcpus. More specifically, the technique called Constant BandWidth Server (CBS) could easily be implemented.
Outcomes: Not specified, project outcomes


SEDF Multiprocessor Support

Date of insert: 08/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Dario Faggioli <dario.faggioli@citrix.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: The SEDF scheduler, within Xen, does not properly handle SMP systems, unless specific vcpu pinning is specified by the user. That is a big limitation of the current implementation, especially since EDF (the algorithm the scheduler uses) could be easily extended to work in that situations. The first thing to do would be turn from using one SEDF runqueue per processor one runqueue per "cluster of processors" (like for instance using one runqueue per-L3, as scredit2 is doing). That would already increase the effectiveness of the scheduler on current hardware a lot. After that, a mechanism for balancing and migrating vcpus among different runqueues can be designed and implemented.
Outcomes: Not specified, project outcomes


Integrating NUMA and Tmem

Date of insert: 08/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Dario Faggioli <dario.faggioli@citrix.com>, Dan Magenheimer <dan.magenheimer_AT_oracle_DOT_com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Trascendent memory (Tmem) as a mechanism for discriminating between frequently and infrequently used data, and thus helping allocating them properly. It would be interesting to investigate and implement all the necessary mechanisms to take advantage of this and improve performances of Tmem enabled guests running on NUMA machines. Some more details here.
Outcomes: Not specified, project outcomes

Performance

Performance tools overhaul

Date of insert: 02/08/2012; Verified: Not updated in 2020; GSoC: Unknown
Technical contact: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Mailing list/forum for project: xen-devel@
IRC channel for project: #xen-devel
Difficulty: Unknown
Skills Needed: Unknown
Description: Generally, works on the performance tool themselves should be listes separately to the Xen_Profiling:_oprofile_and_perf wiki page.
Outcomes: Not specified, project outcomes

Xen Cloud Platform (XCP) and XAPI projects

There are separate wiki pages about XCP and XAPI related projects. Make sure you check these out aswell!


Quick links to changelogs of the various Xen related repositories/trees

Please see XenRepositories wiki page!