Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

On 14/02/2014 07:07, Andres Lagar-Cavilla wrote:
>> Hi all,
>>
>> I created http://wiki.xen.org/wiki/GSoc_2014 based on the project list
>>
>> Unless you guys step up, I will move all projects that have no
>> * level of difficulty
>> * skills needed
>> * outcomes
>> into http://wiki.xen.org/wiki/GSoc_2014#List_of_projects_that_need_more_work
> Hi Lars,
> I updated the two projects I submitted which got moved down to the "need more work" list. I believe they are fully specified now.
>
> Sorry for last minute update -- on US west coast.
>
> Best. Thanks for shepherding this.
>
> Andres
Thank you. Don't wait for me to move stuff into the right section. If 
you feel it is ready, move it up.

Actually, we can and should make modifications in the next few weeks, 
while the GSoC mentor organization applications are reviewed. Activity 
and participation is good. That is entirely OK. I will probably go 
through the "need more work" list and make concrete comments and 
suggestions for improvement.

Regards
Lars

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

Hi all,
I have not gotten any reply to this thread. I saw Wei Lui and Andrés 
Lagar-Cavilla make changes to the project list. Please go through the 
items below and make changes as suggested. Otherwise, our chances to get 
into GSoC 2014 will be relatively slim.
Lars

On 20/01/2014 09:18, Lars Kurth wrote:
> Hi all,
>
> the GSoC application deadline is coming up : Feb 2014. If we want to 
> have any chance of getting accepted this year, we ought to get our 
> project list into good shape. The project list and how the project and 
> menters present themselves has a bigger impact on whether we get 
> accepted than the actual application.
>
> Also, I would like to add a mentor section this year: a short bio, 
> what the mentor cares about and a picture. This will help make the 
> project list more real.
>
> We have *4 weeks* to do this. The bar for GSoC has been getting 
> increasingly high. I know, we are tied down with Xen 4.4, but this is 
> something you need to do if you want the Xen Project to participate.
>
> a) Please, update 
> http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently 
> (these need to be in good shape *before* the application). What I need 
> you to do is:
> a.1) Remove items that are done
> a.2) Add new work items : we ought to have a few sexy topics on say 
> Real-time, mobile and some of the other segments (assuming we can get HW)
> a.3) All project proposals need to be peer reviewed *and* clear ... 
> The peer review process for projects we put in place last year worked 
> well, by which we had past mentors sign of project proposals that were 
> in good enough state.
>
> b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
> get these listed on the respective other programs. And we should link 
> to these from our project page.
>
> Best Regards
> Lars
> P.S.: I will also see whether we can participate as Xen Project under 
> the LF GSoC program, but last year there was push-back and I don't 
> expect this to change
>

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

On Tue, 2014-01-28 at 13:54 +0000, Lars Kurth wrote:
> Hi all,
> I have not gotten any reply to this thread. I saw Wei Lui and Andrés 
> Lagar-Cavilla make changes to the project list. Please go through the 
> items below and make changes as suggested. Otherwise, our chances to get 
> into GSoC 2014 will be relatively slim.

Going through the list, people listed as technical contacts for projects
with GSoC == yes (or unknown) are in the To line. Please reiterate your
interest in mentoring the project(s) and update or remove the entry as
necessary.

I skipped things added recently and I skipped "Xen Cloud Platform (XCP)
and XAPI projects", someone else can pick that up.

And to reiterate what Lars said:

> Add new work items : we ought to have a few sexy topics on say 
> Real-time, mobile and some of the other segments (assuming we can get
> HW)
[...]
> b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
> get these listed on the respective other programs. And we should link 
> to these from our project page.

The list:

Pasi:
      * Implement Xen PVSCSI support in xl/libxl toolstack
      * Implement Xen PVUSB support in xl/libxl toolstack

        Both have unanswered questions posed by Lars in January 2013.
        
Konrad:
      * Block backend/frontend improvements

        I suspect a bunch of these are done? (Also CC Roger, who may
        have done them...)
        
        Was in the list twice, they looked identical so I nuked one.
        
      * Utilize Intel QuickPath on network and block path.

        No comments etc, but sounds advanced for a GSoC student, plus
        its unclear when such hardware became available, are they likely
        to have it? It sounds like it might also be quite high end.
        
      * perf working with Xen

        Done/in progress by Boris I think
        
      * PAT writecombine fixup

        Did I see a fix for this go past? GSoC == unknown?
        
      * Parallel xenwatch

        Bit sparse on details, GSOC == unknown

      * Microcode uploader implementation
        
        Done I think?

      * Integrating NUMA and Tmem
        
        Lists Dan as co-maintainer -- Konrad do you want to propose this
        to the new tmem guy (I've forgotten his name)
        
      * Performance tools overhaul

        Bit vague. And has some of this been done?

      * "Upstream bugs"

        There were 4 of these, dating back to 2012, I don't think this
        list is a good place to track bugs and it seems like at least
        some of them are now obsolete. So I've nuked the lot. If they
        are still relevant I think it would be best to get them into the
        bug tracker.
        
Ben:
      * dom0 kgdb support

        Is this for GSoC?

George:

      * Introducing PowerClamp-like driver for Xen

        I don't think this has been done?

Dario:
      * NUMA effects on inter-VM communication and on multi-VM workloads

        I think this was under way as part of the GNOME Outreach
        program. In that case perhaps it needs updating to reflect what
        has been done and what still needs to be done?
        
      * Integrating NUMA and Tmem

        Lists Dan as co-maintainer -- covered under Konrad's name above.
        
      * Is Xen ready for the Real-Time/Embedded World?
                
        Sounds a bit blue sky? Now that there is active interest in this
        on ARM perhaps a few concrete projects could be proposed to
        replace it?

Andy:

      * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
        allocations

        Sounds too hard for a GSoC to me. Would need fleshing out in any
        case.
        
      * CPU/RAM/PCI diagram tool

        Does this not already exist somewhere?
        
Paul:

      * HVM per-event-channel interrupts

        Might be easier now that Windows PV drivers are opened up?

Roger:
      * Refactor Linux hotplug scripts

        You did some of this I think?
        
Ian C:

      * XL to XCP VM motion

        Perhaps this could be broadened into VM transport between XL and
        other things too -- e.g. libvirt?

Stefano:

      * VM Snapshots

        Still a good project I think
        
George:

      * Allowing guests to boot with a passed-through GPU as the primary
        display

        This seems like a bit of a rathole for a GSoC student to me...
        
      * Advanced Scheduling Parameters
        
        Still to do?

Santosh:

      * KDD (Windows Debugger Stub) enhancements
        
Dave

      * Create a tiny VM for easy load testing

        Someone was looking at this I think?
        
Ian J:

      * Testing PV and HVM installs of Debian using debian-installer
      * Testing NetBSD

        BSD is done I think, and I'm looking at Debian Installer stuff
        myself. I've removed these.


Phew!
Ian.



> Lars
> 
> On 20/01/2014 09:18, Lars Kurth wrote:
> > Hi all,
> >
> > the GSoC application deadline is coming up : Feb 2014. If we want to 
> > have any chance of getting accepted this year, we ought to get our 
> > project list into good shape. The project list and how the project and 
> > menters present themselves has a bigger impact on whether we get 
> > accepted than the actual application.
> >
> > Also, I would like to add a mentor section this year: a short bio, 
> > what the mentor cares about and a picture. This will help make the 
> > project list more real.
> >
> > We have *4 weeks* to do this. The bar for GSoC has been getting 
> > increasingly high. I know, we are tied down with Xen 4.4, but this is 
> > something you need to do if you want the Xen Project to participate.
> >
> > a) Please, update 
> > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently 
> > (these need to be in good shape *before* the application). What I need 
> > you to do is:
> > a.1) Remove items that are done
> > a.2) Add new work items : we ought to have a few sexy topics on say 
> > Real-time, mobile and some of the other segments (assuming we can get HW)
> > a.3) All project proposals need to be peer reviewed *and* clear ... 
> > The peer review process for projects we put in place last year worked 
> > well, by which we had past mentors sign of project proposals that were 
> > in good enough state.
> >
> > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
> > get these listed on the respective other programs. And we should link 
> > to these from our project page.
> >
> > Best Regards
> > Lars
> > P.S.: I will also see whether we can participate as Xen Project under 
> > the LF GSoC program, but last year there was push-back and I don't 
> > expect this to change
> >
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel



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

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ben Guthro]

________________________________________
From: Ian Campbell
Sent: Wednesday, February 05, 2014 9:09 AM
To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson
Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org
Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014


> Ben:
>      * dom0 kgdb support
>
>        Is this for GSoC?

This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here.

That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project.

Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net)


Ben

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Konrad Rzeszutek Wilk]

On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote:
> 
> ________________________________________
> From: Ian Campbell
> Sent: Wednesday, February 05, 2014 9:09 AM
> To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson
> Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org
> Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014
> 
> 
> > Ben:
> >      * dom0 kgdb support
> >
> >        Is this for GSoC?
> 
> This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here.

And it actually works!
> 
> That said, Fri is my last day working for Citrix (and consequently, on Xen) - and I'll be moving on to a Start-up company again, so someone else would need to sponsor this project.
> 
> Naturally, I'll be available via my Non-Citrix email address (ben@guthro.net)
> 
> 
> Ben

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

On Wed, 2014-02-05 at 09:29 -0500, Konrad Rzeszutek Wilk wrote:
> On Wed, Feb 05, 2014 at 02:18:40PM +0000, Ben Guthro wrote:
> > 
> > ________________________________________
> > From: Ian Campbell
> > Sent: Wednesday, February 05, 2014 9:09 AM
> > To: lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli; Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Santosh Jodh; Ian Jackson
> > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-devel@lists.xenproject.org
> > Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014
> > 
> > 
> > > Ben:
> > >      * dom0 kgdb support
> > >
> > >        Is this for GSoC?
> > 
> > This has been on there a while, and could be a GSoC project - there has been some development in the Xen IPI support since this was written, so it may work better than advertised here.
> 
> And it actually works!

OK, I'll nuke it from the list hten, thanks!

> > 
> > That said, Fri is my last day working for Citrix (and consequently,
> on Xen) - and I'll be moving on to a Start-up company again,

Good luck!

Ian.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Konrad Rzeszutek Wilk]

On Wed, Feb 05, 2014 at 02:09:08PM +0000, Ian Campbell wrote:
> On Tue, 2014-01-28 at 13:54 +0000, Lars Kurth wrote:
> > Hi all,
> > I have not gotten any reply to this thread. I saw Wei Lui and Andrés 
> > Lagar-Cavilla make changes to the project list. Please go through the 
> > items below and make changes as suggested. Otherwise, our chances to get 
> > into GSoC 2014 will be relatively slim.
> 
> Going through the list, people listed as technical contacts for projects
> with GSoC == yes (or unknown) are in the To line. Please reiterate your
> interest in mentoring the project(s) and update or remove the entry as
> necessary.
> 
> I skipped things added recently and I skipped "Xen Cloud Platform (XCP)
> and XAPI projects", someone else can pick that up.
> 
> And to reiterate what Lars said:
> 
> > Add new work items : we ought to have a few sexy topics on say 
> > Real-time, mobile and some of the other segments (assuming we can get
> > HW)
> [...]
> > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
> > get these listed on the respective other programs. And we should link 
> > to these from our project page.
> 
> The list:
> 
> Pasi:
>       * Implement Xen PVSCSI support in xl/libxl toolstack
>       * Implement Xen PVUSB support in xl/libxl toolstack
> 
>         Both have unanswered questions posed by Lars in January 2013.
>         
> Konrad:
>       * Block backend/frontend improvements
> 
>         I suspect a bunch of these are done? (Also CC Roger, who may
>         have done them...)
>         
>         Was in the list twice, they looked identical so I nuked one.
>         

<nods>
>       * Utilize Intel QuickPath on network and block path.
> 
>         No comments etc, but sounds advanced for a GSoC student, plus
>         its unclear when such hardware became available, are they likely
>         to have it? It sounds like it might also be quite high end.
>         
>       * perf working with Xen
> 
>         Done/in progress by Boris I think

<nods>
>         
>       * PAT writecombine fixup
> 
>         Did I see a fix for this go past? GSoC == unknown?

No. Still looking for a victi^H^H^Hvolunteer.

>         
>       * Parallel xenwatch
> 
>         Bit sparse on details, GSOC == unknown

That would still be nice. It came from talking to Matt from Amazon. He
was saying that having only one xenwatch thread slows things down for
a medium to big server with lots of guests. Making multiple
xenwatch threads to process XenBus requests in parallel would be
a good improvement.

> 
>       * Microcode uploader implementation
>         
>         Done I think?

<nods>
> 
>       * Integrating NUMA and Tmem
>         
>         Lists Dan as co-maintainer -- Konrad do you want to propose this
>         to the new tmem guy (I've forgotten his name)

Bob Liu. Yes, lets rope him in.
>         
>       * Performance tools overhaul
> 
>         Bit vague. And has some of this been done?

I can't remember what that is.
> 
>       * "Upstream bugs"
> 
>         There were 4 of these, dating back to 2012, I don't think this
>         list is a good place to track bugs and it seems like at least
>         some of them are now obsolete. So I've nuked the lot. If they
>         are still relevant I think it would be best to get them into the
>         bug tracker.

OK, lets nuke them.

We could also add the:

VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel.

MSI multi-vector for Linux upstream kernel.

Thought those are mostly just putting pieces together and repost them
so no "new" development.

>         
> Ben:
>       * dom0 kgdb support
> 
>         Is this for GSoC?
> 
> George:
> 
>       * Introducing PowerClamp-like driver for Xen
> 
>         I don't think this has been done?
> 
> Dario:
>       * NUMA effects on inter-VM communication and on multi-VM workloads
> 
>         I think this was under way as part of the GNOME Outreach
>         program. In that case perhaps it needs updating to reflect what
>         has been done and what still needs to be done?
>         
>       * Integrating NUMA and Tmem
> 
>         Lists Dan as co-maintainer -- covered under Konrad's name above.
>         
>       * Is Xen ready for the Real-Time/Embedded World?
>                 
>         Sounds a bit blue sky? Now that there is active interest in this
>         on ARM perhaps a few concrete projects could be proposed to
>         replace it?
> 
> Andy:
> 
>       * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>         allocations
> 
>         Sounds too hard for a GSoC to me. Would need fleshing out in any
>         case.
>         
>       * CPU/RAM/PCI diagram tool
> 
>         Does this not already exist somewhere?
>         
> Paul:
> 
>       * HVM per-event-channel interrupts
> 
>         Might be easier now that Windows PV drivers are opened up?
> 
> Roger:
>       * Refactor Linux hotplug scripts
> 
>         You did some of this I think?
>         
> Ian C:
> 
>       * XL to XCP VM motion
> 
>         Perhaps this could be broadened into VM transport between XL and
>         other things too -- e.g. libvirt?
> 
> Stefano:
> 
>       * VM Snapshots
> 
>         Still a good project I think
>         
> George:
> 
>       * Allowing guests to boot with a passed-through GPU as the primary
>         display
> 
>         This seems like a bit of a rathole for a GSoC student to me...
>         
>       * Advanced Scheduling Parameters
>         
>         Still to do?
> 
> Santosh:
> 
>       * KDD (Windows Debugger Stub) enhancements
>         
> Dave
> 
>       * Create a tiny VM for easy load testing
> 
>         Someone was looking at this I think?
>         
> Ian J:
> 
>       * Testing PV and HVM installs of Debian using debian-installer
>       * Testing NetBSD
> 
>         BSD is done I think, and I'm looking at Debian Installer stuff
>         myself. I've removed these.
> 
> 
> Phew!
> Ian.
> 
> 
> 
> > Lars
> > 
> > On 20/01/2014 09:18, Lars Kurth wrote:
> > > Hi all,
> > >
> > > the GSoC application deadline is coming up : Feb 2014. If we want to 
> > > have any chance of getting accepted this year, we ought to get our 
> > > project list into good shape. The project list and how the project and 
> > > menters present themselves has a bigger impact on whether we get 
> > > accepted than the actual application.
> > >
> > > Also, I would like to add a mentor section this year: a short bio, 
> > > what the mentor cares about and a picture. This will help make the 
> > > project list more real.
> > >
> > > We have *4 weeks* to do this. The bar for GSoC has been getting 
> > > increasingly high. I know, we are tied down with Xen 4.4, but this is 
> > > something you need to do if you want the Xen Project to participate.
> > >
> > > a) Please, update 
> > > http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently 
> > > (these need to be in good shape *before* the application). What I need 
> > > you to do is:
> > > a.1) Remove items that are done
> > > a.2) Add new work items : we ought to have a few sexy topics on say 
> > > Real-time, mobile and some of the other segments (assuming we can get HW)
> > > a.3) All project proposals need to be peer reviewed *and* clear ... 
> > > The peer review process for projects we put in place last year worked 
> > > well, by which we had past mentors sign of project proposals that were 
> > > in good enough state.
> > >
> > > b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
> > > get these listed on the respective other programs. And we should link 
> > > to these from our project page.
> > >
> > > Best Regards
> > > Lars
> > > P.S.: I will also see whether we can participate as Xen Project under 
> > > the LF GSoC program, but last year there was push-back and I don't 
> > > expect this to change
> > >
> > 
> > 
> > _______________________________________________
> > Xen-devel mailing list
> > Xen-devel@lists.xen.org
> > http://lists.xen.org/xen-devel
> 
> 

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

On Wed, 2014-02-05 at 09:34 -0500, Konrad Rzeszutek Wilk wrote:
> >         
> >       * Parallel xenwatch
> > 
> >         Bit sparse on details, GSOC == unknown
> 
> That would still be nice. It came from talking to Matt from Amazon. He
> was saying that having only one xenwatch thread slows things down for
> a medium to big server with lots of guests. Making multiple
> xenwatch threads to process XenBus requests in parallel would be
> a good improvement.

Would need to be careful about exposing cases of insufficient locking in
the existing code.

> 
> > 
> >       * Microcode uploader implementation
> >         
> >         Done I think?
> 
> <nods>

Nuked
     
> >       * Performance tools overhaul
> > 
> >         Bit vague. And has some of this been done?
> 
> I can't remember what that is.

OK, I nuked it -- a new project can always be added if you remember what
it was.

> > 
> >       * "Upstream bugs"
> > 
> >         There were 4 of these, dating back to 2012, I don't think this
> >         list is a good place to track bugs and it seems like at least
> >         some of them are now obsolete. So I've nuked the lot. If they
> >         are still relevant I think it would be best to get them into the
> >         bug tracker.
> 
> OK, lets nuke them.

Done.

> 
> We could also add the:
> 
> VCPUOP_register_vcpu_time_memory_area support in Linux upstream kernel.
> 
> MSI multi-vector for Linux upstream kernel.
> 
> Thought those are mostly just putting pieces together and repost them
> so no "new" development.

Not really suitable for this list then IMHO.

Ian.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Andrew Cooper]

On 05/02/14 14:09, Ian Campbell wrote:
>
> Andy:
>
>       * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>         allocations
>
>         Sounds too hard for a GSoC to me. Would need fleshing out in any
>         case.

Malcolm made a prototype for this on the first day of the Hackathon.  It
can disappear.

>         
>       * CPU/RAM/PCI diagram tool
>
>         Does this not already exist somewhere?

Not as far as I (or my ability to google) am aware.

My furrowing into hwloc interacting with Xen and libxc is a start to all
of this, but it is still very much in my copious free time and there is
more than enough other work which could be done if someone were interested.

~Andrew

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
> On 05/02/14 14:09, Ian Campbell wrote:
> >
> > Andy:
> >
> >       * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
> >         allocations
> >
> >         Sounds too hard for a GSoC to me. Would need fleshing out in any
> >         case.
> 
> Malcolm made a prototype for this on the first day of the Hackathon.  It
> can disappear.

Removed.

> >       * CPU/RAM/PCI diagram tool
> >
> >         Does this not already exist somewhere?
> 
> Not as far as I (or my ability to google) am aware.
> 
> My furrowing into hwloc interacting with Xen and libxc is a start to all
> of this, but it is still very much in my copious free time and there is
> more than enough other work which could be done if someone were interested.

OK, left in place.

This could conceivably be done under another umbrella such as the Linux
one too, since it seems generic.

Ian.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Andrew Cooper]

On 05/02/14 14:45, Ian Campbell wrote:
> On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
>> On 05/02/14 14:09, Ian Campbell wrote:
>>> Andy:
>>>
>>>       * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>>>         allocations
>>>
>>>         Sounds too hard for a GSoC to me. Would need fleshing out in any
>>>         case.
>> Malcolm made a prototype for this on the first day of the Hackathon.  It
>> can disappear.
> Removed.
>
>>>       * CPU/RAM/PCI diagram tool
>>>
>>>         Does this not already exist somewhere?
>> Not as far as I (or my ability to google) am aware.
>>
>> My furrowing into hwloc interacting with Xen and libxc is a start to all
>> of this, but it is still very much in my copious free time and there is
>> more than enough other work which could be done if someone were interested.
> OK, left in place.
>
> This could conceivably be done under another umbrella such as the Linux
> one too, since it seems generic.
>
> Ian.
>
>

For native Linux, hwloc kinda already does this already - certainly the
CPU and PCI bits.  Under Xen there are quite a few areas needing
improvement, which will require active development work.

~Andrew

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

(trimming cc, most people are presumably not interested)

On Wed, 2014-02-05 at 14:49 +0000, Andrew Cooper wrote:
> On 05/02/14 14:45, Ian Campbell wrote:
> > On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
> >> On 05/02/14 14:09, Ian Campbell wrote:
> >>> Andy:
> >>>
> >>>       * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
> >>>         allocations
> >>>
> >>>         Sounds too hard for a GSoC to me. Would need fleshing out in any
> >>>         case.
> >> Malcolm made a prototype for this on the first day of the Hackathon.  It
> >> can disappear.
> > Removed.
> >
> >>>       * CPU/RAM/PCI diagram tool
> >>>
> >>>         Does this not already exist somewhere?
> >> Not as far as I (or my ability to google) am aware.
> >>
> >> My furrowing into hwloc interacting with Xen and libxc is a start to all
> >> of this, but it is still very much in my copious free time and there is
> >> more than enough other work which could be done if someone were interested.
> > OK, left in place.
> >
> > This could conceivably be done under another umbrella such as the Linux
> > one too, since it seems generic.
> >
> > Ian.
> >
> >
> 
> For native Linux, hwloc kinda already does this already - certainly the
> CPU and PCI bits.

That's what I meant by "does this not alreayd exist somewhere". So it
sounds like extending hwloc is the right answer, the blurb should
reflect this and list the specific things which it is lacking.

Can you update the description please?

>   Under Xen there are quite a few areas needing
> improvement, which will require active development work.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

Hi all,

I created http://wiki.xen.org/wiki/GSoc_2014 based on the project list

Unless you guys step up, I will move all projects that have no
* level of difficulty
* skills needed
* outcomes
into http://wiki.xen.org/wiki/GSoc_2014#List_of_projects_that_need_more_work

I made a start on this and will do more on the weekend and/or monday. I 
will also sort, such that easy projects come first.

I am about to submit the application in the next two hours

Regards

On 05/02/2014 14:52, Ian Campbell wrote:
> (trimming cc, most people are presumably not interested)
>
> On Wed, 2014-02-05 at 14:49 +0000, Andrew Cooper wrote:
>> On 05/02/14 14:45, Ian Campbell wrote:
>>> On Wed, 2014-02-05 at 14:40 +0000, Andrew Cooper wrote:
>>>> On 05/02/14 14:09, Ian Campbell wrote:
>>>>> Andy:
>>>>>
>>>>>        * IOMMU control for SWIOTLB, to avoid dom0 copy of all >4K DMA
>>>>>          allocations
>>>>>
>>>>>          Sounds too hard for a GSoC to me. Would need fleshing out in any
>>>>>          case.
>>>> Malcolm made a prototype for this on the first day of the Hackathon.  It
>>>> can disappear.
>>> Removed.
>>>
>>>>>        * CPU/RAM/PCI diagram tool
>>>>>
>>>>>          Does this not already exist somewhere?
>>>> Not as far as I (or my ability to google) am aware.
>>>>
>>>> My furrowing into hwloc interacting with Xen and libxc is a start to all
>>>> of this, but it is still very much in my copious free time and there is
>>>> more than enough other work which could be done if someone were interested.
>>> OK, left in place.
>>>
>>> This could conceivably be done under another umbrella such as the Linux
>>> one too, since it seems generic.
>>>
>>> Ian.
>>>
>>>
>> For native Linux, hwloc kinda already does this already - certainly the
>> CPU and PCI bits.
> That's what I meant by "does this not alreayd exist somewhere". So it
> sounds like extending hwloc is the right answer, the blurb should
> reflect this and list the specific things which it is lacking.
>
> Can you update the description please?
>
>>    Under Xen there are quite a few areas needing
>> improvement, which will require active development work.
>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[George Dunlap]

On Wed, Feb 5, 2014 at 2:09 PM, Ian Campbell <Ian.Campbell@citrix.com> wrote:

> George:
>
>       * Introducing PowerClamp-like driver for Xen
>
>         I don't think this has been done?

Not that I'm aware of.

> George:
>
>       * Allowing guests to boot with a passed-through GPU as the primary
>         display
>
>         This seems like a bit of a rathole for a GSoC student to me...

Possibly.  I thought it might be a bit more attractive project, but
maybe that's a bad thing...

>       * Advanced Scheduling Parameters
>
>         Still to do?

Yes.

 -George

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Santosh Jodh]

> 
> Santosh:
> 
>       * KDD (Windows Debugger Stub) enhancements
> 
[Santosh Jodh] I believe this is still a good GSOC project. However, in light of my new direction, I am not sure if I will be able to mentor. Don’t know if Paul or someone else on the Windows team would want to sponsor this.

Regards,
Santosh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Paul Durrant]

> -----Original Message-----
> From: Santosh Jodh
> Sent: 06 February 2014 16:44
> To: Ian Campbell; lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli;
> Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Ian
> Jackson
> Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-
> devel@lists.xenproject.org
> Subject: RE: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14
> 2014
> 
> >
> > Santosh:
> >
> >       * KDD (Windows Debugger Stub) enhancements
> >
> [Santosh Jodh] I believe this is still a good GSOC project. However, in light of
> my new direction, I am not sure if I will be able to mentor. Don’t know if Paul
> or someone else on the Windows team would want to sponsor this.
> 

Yes, it's still a worthy project. I'd be happy to sponsor.

  Paul

> Regards,
> Santosh
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Campbell]

On Thu, 2014-02-06 at 17:43 +0000, Paul Durrant wrote:
> > -----Original Message-----
> > From: Santosh Jodh
> > Sent: 06 February 2014 16:44
> > To: Ian Campbell; lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli;
> > Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Ian
> > Jackson
> > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-
> > devel@lists.xenproject.org
> > Subject: RE: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14
> > 2014
> > 
> > >
> > > Santosh:
> > >
> > >       * KDD (Windows Debugger Stub) enhancements
> > >
> > [Santosh Jodh] I believe this is still a good GSOC project. However, in light of
> > my new direction, I am not sure if I will be able to mentor. Don’t know if Paul
> > or someone else on the Windows team would want to sponsor this.
> > 
> 
> Yes, it's still a worthy project. I'd be happy to sponsor.

Do you mean "mentor"?

Can you update hte project on the wiki please.

Ian.



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

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Paul Durrant]

> -----Original Message-----
> From: Ian Campbell
> Sent: 06 February 2014 17:44
> To: Paul Durrant
> Cc: Santosh Jodh; lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli;
> Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Ian Jackson; xen-
> devel@lists.xen.org; xen-api@lists.xen.org; mirageos-
> devel@lists.xenproject.org
> Subject: Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14
> 2014
> 
> On Thu, 2014-02-06 at 17:43 +0000, Paul Durrant wrote:
> > > -----Original Message-----
> > > From: Santosh Jodh
> > > Sent: 06 February 2014 16:44
> > > To: Ian Campbell; lars.kurth@xen.org; Roger Pau Monne; Dario Faggioli;
> > > Konrad Rzeszutek Wilk; Ben Guthro; Andrew Cooper; Paul Durrant; Ian
> > > Jackson
> > > Cc: xen-devel@lists.xen.org; xen-api@lists.xen.org; mirageos-
> > > devel@lists.xenproject.org
> > > Subject: RE: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline
> Feb 14
> > > 2014
> > >
> > > >
> > > > Santosh:
> > > >
> > > >       * KDD (Windows Debugger Stub) enhancements
> > > >
> > > [Santosh Jodh] I believe this is still a good GSOC project. However, in light
> of
> > > my new direction, I am not sure if I will be able to mentor. Don’t know if
> Paul
> > > or someone else on the Windows team would want to sponsor this.
> > >
> >
> > Yes, it's still a worthy project. I'd be happy to sponsor.
> 
> Do you mean "mentor"?

Yes, whatever the appropriate term is.

> 
> Can you update hte project on the wiki please.
> 

Sure.

  Paul

> Ian.
> 

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

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Roger Pau Monné]

On 05/02/14 15:09, Ian Campbell wrote:
> Roger:
>       * Refactor Linux hotplug scripts
> 
>         You did some of this I think?

No, I've added a block-iscsi script, but I did not refactor the other
ones. It is still valid, however, I'm not sure it's attractive from a
GSoC point of view. I'm going to leave it anyway in case someone is
interested.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Ian Jackson]

Roger Pau Monné writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014"):
> On 05/02/14 15:09, Ian Campbell wrote:
> > Roger:
> >       * Refactor Linux hotplug scripts
> > 
> >         You did some of this I think?
> 
> No, I've added a block-iscsi script, but I did not refactor the other
> ones. It is still valid, however, I'm not sure it's attractive from a
> GSoC point of view. I'm going to leave it anyway in case someone is
> interested.

Who is actually submitting our GSOC application ?

Ian.

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monné writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.
I have submitted it.  Please continue working on and refining 
http://wiki.xen.org/wiki/GSoc_2014
If you feel that a project should be moved into 
http://wiki.xen.org/wiki/GSoc_2014#List_of_peer_reviewed_Projects please 
do so

Regards
Lars

Re: Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

Hi all,

I just combed through the list of projects, and to be honest most can be 
improved.

Please put yourself into the shoes of someone who
a) is a student and
b) has not worked on Xen before.
* If you use acronyms, please point to the definitions.
* If you refer to specs, please link to the specs.
* If you refer to a location to the code, why not link to it.
c) breaking down the project into more manageable chunks will also help

Anyway, Google is reviewing applications this week. Changes to the 
project page that are made this week will still make an impact. Accepted 
orgs are announced on the 24th.

Regards
Lars

On 13/02/2014 17:13, Ian Jackson wrote:
> Roger Pau Monné writes ("Re: [Xen-devel] Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014"):
>> On 05/02/14 15:09, Ian Campbell wrote:
>>> Roger:
>>>        * Refactor Linux hotplug scripts
>>>
>>>          You did some of this I think?
>> No, I've added a block-iscsi script, but I did not refactor the other
>> ones. It is still valid, however, I'm not sure it's attractive from a
>> GSoC point of view. I'm going to leave it anyway in case someone is
>> interested.
> Who is actually submitting our GSOC application ?
>
> Ian.

Prepping for GSOC 2014 [URGENT] - deadline Feb 14 2014

[Lars Kurth]

Hi all,

the GSoC application deadline is coming up : Feb 2014. If we want to 
have any chance of getting accepted this year, we ought to get our 
project list into good shape. The project list and how the project and 
menters present themselves has a bigger impact on whether we get 
accepted than the actual application.

Also, I would like to add a mentor section this year: a short bio, what 
the mentor cares about and a picture. This will help make the project 
list more real.

We have *4 weeks* to do this. The bar for GSoC has been getting 
increasingly high. I know, we are tied down with Xen 4.4, but this is 
something you need to do if you want the Xen Project to participate.

a) Please, update 
http://wiki.xenproject.org/wiki/Xen_Development_Projects urgently (these 
need to be in good shape *before* the application). What I need you to 
do is:
a.1) Remove items that are done
a.2) Add new work items : we ought to have a few sexy topics on say 
Real-time, mobile and some of the other segments (assuming we can get HW)
a.3) All project proposals need to be peer reviewed *and* clear ... The 
peer review process for projects we put in place last year worked well, 
by which we had past mentors sign of project proposals that were in good 
enough state.

b) Anyone who has some kernel/linux/bsd/distro/qemu work-items, should 
get these listed on the respective other programs. And we should link to 
these from our project page.

Best Regards
Lars
P.S.: I will also see whether we can participate as Xen Project under 
the LF GSoC program, but last year there was push-back and I don't 
expect this to change