The printable version is no longer supported and may have rendering errors. Please update your browser bookmarks and please use the default browser print function instead.
When and Where ?
We confirmed the Xen Hackathon for May 16-17, 2013 in Dublin Ireland.
- May 16th: 9AM to 5PM
- May 17th: 9AM to 5PM
More Information
Topics to Discuss, Code, Work on, ... at the Hackathon
Instructions
Topics
Xen on ARM "Portathon"
Date of insert: 12/03/2013; Verified: Not updated in 2020; GSoC: N/A |
Technical contact: Ian Campbell |
Mailing list/forum for project: xen-devel@ |
IRC channel for project: #xen-devel |
Difficulty: Not too hard if you are familiar with the hardware and have Linux running |
Skills Needed: Mostly C |
Description: Xen on ARM has reached the point where it is becoming reasonable to port it to a wider set of hardware. The idea of this session would be to take advantage of the presence of the Xen on ARM developers to port Xen to your hardware. In order to participate you will need:
- Access to a hardware platform which supports the ARM virtualisation extension which you wish to port Xen to.
- Could be local access if hardware is portable, otherwise remote serial and power control will be required
- Software models could also be considered
- An existing functioning port of Linux >3.8 to the platform
- Access to datasheets and/or extensive knowledge of the hardware platform
|
Outcomes: Xen running on some new ARM platforms |
|
Update toolstacks to make use of libxl and/or xl
Date of insert: 12/03/2013; Verified: Not updated in 2020; GSoC: N/A |
Technical contact: Ian Campbell |
Mailing list/forum for project: xen-devel@ |
IRC channel for project: #xen-devel |
Difficulty: Depends on the complexity of the toolstack which needs modifying |
Skills Needed: Some C, perhaps knowledge of the C bindings for the language which the toolstack uses. |
Description: There are various higher-level toolstacks which make direct use of the xend interfaces (either through xm, sxp or XML/RPC). This project offers an opportunity to collaborate on porting toolstacks to use xl or other modern toolstack interfaces.
This project also covers those who wish to use libxl directly to implement their own toolstack or to port an existing toolstack from other lower-level interface (such as libxc) to libxl.
It is expected that participants will be familiar with the internals of the toolstack the wish to port to libxl/xl |
Outcomes: More toolstacks using xl or libxl. |
|
VMFUNC, grant table operations, Intel QuickData engines
Date of insert: 12/03/2013; Verified: Not updated in 2020; GSoC: N/A |
Technical contact: Konrad Rzeszutek Wilk |
Mailing list/forum for project: xen-devel@ |
IRC channel for project: #xen-devel |
Difficulty: Need to read dense Intel docs. |
Skills Needed: Wielding a sharpie. |
Description: Intel has released a new VMX type operations that allows one guest to switch in another guest page-tables. We could utilize this for a backend guest to
switch in the page-tables that the frontend has provided via the ring. Along with the Intel QuickData engine we could keep the contents of these
pages (aka grefs) in the LLC. This is all handwaving at this point and I am hoping to brain-storm the problem and issues we will face. |
Outcomes: Faster performance. |
|
Close Security Vulnerability Process Changes as well as discuss possible mods to the Governance Process
Date of insert: 29/03/2013; Verified: Not updated in 2020; GSoC: N/A |
Technical contact: Lars Kurth |
Mailing list/forum for project: xen-devel@ |
IRC channel for project: #xen-devel |
Difficulty: N/A |
Skills Needed: N/A |
Description: We should take the opportunity of core developers present to close down the proposed Security Vulnerability Process discussion as much as possible. Also, I wanted to discuss whether we can be a little bit more open about membership of the Security Response team (i.e. who is on it, and what the process/mechanism is of becoming a member of the team). And maybe any other security related questions.
I would also like to take the opportunity of discussing possible changes to the governance process. |
Outcomes: Not specified, project outcomes |
|
Confirmed Attendees
|
To Do:
Add a list of confirmed and registered attendees here
|