xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Paulina Szubarczyk <paulinaszubarczyk@gmail.com>
To: "Roger Pau Monné" <roger.pau@citrix.com>
Cc: xen-devel@lists.xenproject.org, mina.naghshnejad@gmail.com
Subject: Re: Outreachy bite-sized tasks
Date: Wed, 23 Mar 2016 17:38:57 +0100	[thread overview]
Message-ID: <CAMQpU2rbchN_5PXVm2bsn41C3LphH-XFFbDrEVL+t2_dFp+hPQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.OSX.2.20.1603231600320.753@mac>

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


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

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

  reply	other threads:[~2016-03-23 16:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-23 15:32 Outreachy bite-sized tasks Roger Pau Monné
2016-03-23 16:38 ` Paulina Szubarczyk [this message]
2016-03-23 18:21   ` Dario Faggioli
2016-04-01 10:05     ` Paulina Szubarczyk
2016-04-01 13:35       ` Roger Pau Monné
2016-04-20 10:06         ` Paulina Szubarczyk
2016-04-25 18:58           ` Konrad Rzeszutek Wilk

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:

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

  git send-email \
    --in-reply-to=CAMQpU2rbchN_5PXVm2bsn41C3LphH-XFFbDrEVL+t2_dFp+hPQ@mail.gmail.com \
    --to=paulinaszubarczyk@gmail.com \
    --cc=mina.naghshnejad@gmail.com \
    --cc=roger.pau@citrix.com \
    --cc=xen-devel@lists.xenproject.org \


* 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).