Re: [Xen-devel] Taking on a Xen development project

[Yang Hongyang <hongyang.yang@xxxxxxxxxxxx>]

On 2015å12æ11æ 01:23, Andrew Cooper wrote:
> On 04/12/15 20:26, jtotto@xxxxxxxxxxxx wrote:
> > Hi,
> >
> > We're a team of three fourth-year undergraduate software engineering
> > students at the University of Waterloo in Canada.  We're in the process
> > of planning for our capstone design project, and are interested in
> > contributing to Xen.  Ideally, we'd like to take on a hypervisor/kernel
> > hacking project with roughly the same scope as a Google Summer of Code
> > project (like the hypervisor or domain support projects described at
> > [0]), following a similar timeline (roughly May to August 2016).  We're
> > all broadly interested in systems programming in C, and have each had
> > relevant academic and internship experiences.
> >
> > Each of projects [1-3] currently on the Wiki look interesting, though
> > we'd be completely open to others as well.  In particular, we'd be open
> > to picking up Ben Catterall's work on HVM x86 deprivileged mode [4].  Do
> > any of these projects seem like a good fit in terms of usefulness to the
> > community and our timeline?  If so, we'd love to communicate more with
> > any maintainers with projects in mind!  We were also hoping to
> > familiarize ourselves with the project by addressing some Coverity
> > issues, if any are open at the moment.
> >
> > Thanks!
> >
> > Harley Armstrong, Chester Lin, Joshua Otto
> Hello - thankyou for your interest.
>
> One area to look at might be the parameters to the live migration
> looping.  As part of the migration v2 rework I did in the 4.6 dev
> period, I left all of that alone, and it is in a working but poor state.
>
> In the past, there have been several research investigations into
> improving the live migration algorithm, such as tracking the rate of
> dirtying of memory, or attempting to resume the domain on the far side
> and fault the final memory across.
I think you mean postcopy here? The hypervisor then needs to maintain
a dirty page bitmap and generate pagefault when a page is not yet
tranferred to the far end.
This feature already merged into QEMU2.5(kvm patch which generates
pagefault also been merged into linux kernel mainline), if you want a
reference, you can take a look at those patches.
This surely is a great aera to work on.

> If you are interested in perusing this, start with reading
> docs/features/migration.pandoc in the Xen tree.
>
> ~Andrew
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxx
> http://lists.xen.org/xen-devel
--
Thanks,
Yang

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel