xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Ian Campbell <Ian.Campbell-Sxgqhf6Nn4DQT0dZR+AlfA@public.gmane.org>
To: xen-devel
	<xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
	xen-api-GuqFBffKawuEi8DpZVb4nw@public.gmane.org
Subject: GSoC 2012 project brainstorming
Date: Wed, 29 Feb 2012 16:53:57 +0000	[thread overview]
Message-ID: <1330534437.4270.143.camel@zakaz.uk.xensource.com> (raw)

Below are a few ideas which have been floating around as potential
projects (or broad subject areas for projects) for GSoC this year.

If you want any more information on any particular item then please ask.
Likewise if you have any ideas of your own please feel free to chip in.

If you think you might be interested in a project, either as mentor or
potential student, then please add it to the wiki page at
http://wiki.xen.org/wiki/GSoC_2012_Ideas

Ian.

TOOLS
-----
- pv grub2
- xapi support in libvirt
- make xapi use libxl
- compile xapi on ARM
- OpenXenManager
- driver domains
- PV dbus
- HA daemon for Remus
- HA daemon for XCP

PERF
----
- Oprofile
- Linux perf tools in guest

HYPERVISOR
----------
- insmod Xen
- event channel limits
- NUMA

MEMORY
------
- disk based memory sharing
- memory scanner
- paging replacing PoD
- VM Fork
- Copy on read (past VDI boot)


IO
--
- PV OpenGL/Gallium
- PV USB
- PV USB3
- PV SCSI
- PVFB in Xorg
- Infiniband


STORAGE
-------
- gluster/ceph plugins


QEMU
----
- BSD libc
- upstream QEMU stubdoms


TESTS
-----
- better web reporting
- more tests
- upstream linux


DISTROS
-------
- packaging stubdoms
- xen on centos6
- driver domains
- figure out the VM format issue
- XSM in distros

             reply	other threads:[~2012-02-29 16:53 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-29 16:53 Ian Campbell [this message]
     [not found] ` <1330534437.4270.143.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-02-29 18:25   ` [Xen-devel] GSoC 2012 project brainstorming Pasi Kärkkäinen
2012-03-12 17:00   ` Konrad Rzeszutek Wilk
     [not found]     ` <20120312170012.GI5369-6K5HmflnPlqSPmnEAIUT9EEOCMrvLtNR@public.gmane.org>
2012-03-12 17:25       ` Ian Campbell
     [not found]         ` <1331573131.23971.165.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-03-14 18:56           ` Konrad Rzeszutek Wilk
2012-03-12 17:48     ` [Xen-API] " Dario Faggioli
2012-03-14 16:59   ` [Xen-devel] " Ian Campbell
     [not found]     ` <1331744386.23971.496.camel-o4Be2W7LfRlXesXXhkcM7miJhflN2719@public.gmane.org>
2012-03-14 17:55       ` Dave Scott
     [not found]         ` <81A73678E76EA642801C8F2E4823AD21D7724CFA2D-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2012-03-15  7:51           ` Ian Campbell
     [not found]             ` <1331797918.13956.27.camel-ztPmHsLffjjnO4AKDKe2m+kiAK3p4hvP@public.gmane.org>
2012-03-15 10:02               ` Dave Scott
     [not found]                 ` <81A73678E76EA642801C8F2E4823AD21D7724CFA32-aFusIB7tbcLeU4JHVX8hdHnr0TU713UqXqFh9Ls21Oc@public.gmane.org>
2012-03-15 10:13                   ` Ian Campbell
2012-03-15 15:11                   ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1330534437.4270.143.camel@zakaz.uk.xensource.com \
    --to=ian.campbell-sxgqhf6nn4dqt0dzr+alfa@public.gmane.org \
    --cc=xen-api-GuqFBffKawuEi8DpZVb4nw@public.gmane.org \
    --cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).