Re: Outreachy bite-sized tasks

[Paulina Szubarczyk <paulinaszubarczyk@gmail.com>]

[-- Attachment #1.1: Type: text/plain, Size: 2416 bytes --]

Hi,

Thank you for the proposed tasks. I would like to work on the second one,
fixing the return codes in xl.

Regards,
Paulina Szubarczyk

On 23 March 2016 at 16:32, Roger Pau Monné <roger.pau@citrix.com> wrote:

> Hello,
>
> First of all, thanks for your interest in the Xen Project, and for wanting
> to participate in Outreachy.
>
> Both of you have expressed interest in the "QEMU xen-blkback performance
> analysis and improvements" Outreachy project, and AFAIK both of you still
> need to perform your initial contribution.
>
> I've found a couple of small tasks that you can perform and should allow
> you to complete your initial contribution to the project:
>
>  - The first one is related to xenalyze, and it consist in creating a
>    header file that can be shared by both the Xen kernel and xenalyze.
>    You will need to move the TRC_ defines found in sched_credit.c and
>    sched_credit2.c to a header that's shared with xenalyze and then
>    replace the usage of TRC_SCHED_CLASS_EVT with the defines in the header
>    file [0].
>
>  - The second one consist in fixing the return codes of certain xl
>    commands. There are commands in xl that will return 0 (SUCCESS) even
>    when failing, which makes it very hard to write scripts that make use
>    of xl. A list of those commands can be found in [1], together with some
>    preliminary patches. Please note that those patches have comments that
>    you will need to address, and that you should also need to preserve the
>    original authorship of the patches plus yours.
>
> I encourage you to read the wiki page about sending patches to xen-devel
> [2], it should guide you through your first steps on using git and
> creating suitable patches.
>
> Also, please note that this is an open source project, so you will need to
> coordinate in order to figure out which task are you going to take, in
> order to avoid clashes or duplication of efforts.
>
> If you have further questions, either reply to this thread (keeping
> the xen-devel mailing list on the Cc), or feel free to start another one
> if you think it's more suited.
>
> Roger.
>
> [0]
> http://lists.xenproject.org/archives/html/xen-devel/2016-02/msg02624.html
> [1]
> http://lists.xenproject.org/archives/html/xen-devel/2015-12/msg02246.html
> [2] http://wiki.xenproject.org/wiki/Submitting_Xen_Project_Patches
>

[-- Attachment #1.2: Type: text/html, Size: 3307 bytes --]

[-- Attachment #2: Type: text/plain, Size: 126 bytes --]

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