From mboxrd@z Thu Jan 1 00:00:00 1970 From: Paulina Szubarczyk Subject: Re: Outreachy bite-sized tasks Date: Wed, 23 Mar 2016 17:38:57 +0100 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============3456583683238587119==" Return-path: Received: from mail6.bemta14.messagelabs.com ([193.109.254.103]) by lists.xenproject.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ailoC-0002x9-7R for xen-devel@lists.xenproject.org; Wed, 23 Mar 2016 16:39:00 +0000 Received: by mail-lf0-f52.google.com with SMTP id q73so13383988lfe.2 for ; Wed, 23 Mar 2016 09:38:58 -0700 (PDT) In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Errors-To: xen-devel-bounces@lists.xen.org Sender: "Xen-devel" To: =?UTF-8?Q?Roger_Pau_Monn=C3=A9?= Cc: xen-devel@lists.xenproject.org, mina.naghshnejad@gmail.com List-Id: xen-devel@lists.xenproject.org --===============3456583683238587119== Content-Type: multipart/alternative; boundary=001a113f17d65d2408052eb9f760 --001a113f17d65d2408052eb9f760 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable 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=C3=A9 wrot= e: > Hello, > > First of all, thanks for your interest in the Xen Project, and for wantin= g > 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 heade= r > 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 som= e > preliminary patches. Please note that those patches have comments that > you will need to address, and that you should also need to preserve th= e > 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 t= o > 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 > --001a113f17d65d2408052eb9f760 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Hi,=C2=A0

Thank you for the proposed ta= sks. I would like to work on the second one,=C2=A0
fixing the ret= urn codes in xl.

Regards,=
Paulina Szubarczyk=C2=A0

On 23 March 2016 at 16:32= , Roger Pau Monn=C3=A9 <roger.pau@citrix.com> wrote:
<= blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px= #ccc solid;padding-left:1ex">Hello,

First of all, thanks for your interest in the Xen Project, and for wanting<= br> to participate in Outreachy.

Both of you have expressed interest in the "QEMU xen-blkback performan= ce
analysis and improvements" Outreachy project, and AFAIK both of you st= ill
need to perform your initial contribution.

I've found a couple of small tasks that you can perform and should allo= w
you to complete your initial contribution to the project:

=C2=A0- The first one is related to xenalyze, and it consist in creating a<= br> =C2=A0 =C2=A0header file that can be shared by both the Xen kernel and xena= lyze.
=C2=A0 =C2=A0You will need to move the TRC_ defines found in sched_credit.c= and
=C2=A0 =C2=A0sched_credit2.c to a header that's shared with xenalyze an= d then
=C2=A0 =C2=A0replace the usage of TRC_SCHED_CLASS_EVT with the defines in t= he header
=C2=A0 =C2=A0file [0].

=C2=A0- The second one consist in fixing the return codes of certain xl
=C2=A0 =C2=A0commands. There are commands in xl that will return 0 (SUCCESS= ) even
=C2=A0 =C2=A0when failing, which makes it very hard to write scripts that m= ake use
=C2=A0 =C2=A0of xl. A list of those commands can be found in [1], together = with some
=C2=A0 =C2=A0preliminary patches. Please note that those patches have comme= nts that
=C2=A0 =C2=A0you will need to address, and that you should also need to pre= serve the
=C2=A0 =C2=A0original 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<= br> 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/Su= bmitting_Xen_Project_Patches

--001a113f17d65d2408052eb9f760-- --===============3456583683238587119== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KWGVuLWRldmVs IG1haWxpbmcgbGlzdApYZW4tZGV2ZWxAbGlzdHMueGVuLm9yZwpodHRwOi8vbGlzdHMueGVuLm9y Zy94ZW4tZGV2ZWwK --===============3456583683238587119==--