From: Ronald Rojas <ronladred@gmail.com>
To: George Dunlap <george.dunlap@citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: New Outreachy Applicant
Date: Thu, 6 Oct 2016 10:26:30 -0400 [thread overview]
Message-ID: <20161006142627.GA6830@fedora> (raw)
In-Reply-To: <CAFLBxZb-o88uBKDY+HgEsDR4Y4v_3TYyLwkfWKTXMuhTj-mUyw@mail.gmail.com>
On Wed, Oct 05, 2016 at 06:44:08PM +0100, George Dunlap wrote:
> On Tue, Oct 4, 2016 at 3:23 PM, George Dunlap <george.dunlap@citrix.com> wrote:
> > Thanks for this -- if you're up for it, let me see what kinds of next
> > steps you can do (obviously when you have the opportunity).
>
> So there are a couple of things we could do next.
>
> * If you want a simple change that you can use to get experience with
> sending patches to the list:
>
> There are a number of instances in tools/libxl/xl_cmdimpl.c where
> where domid is listed as uint32_t (or libxl_domid), but the printf
> specifier is used as '%d'. Change this to '%u'.
>
> * If you want an investigation to do:
>
> At least a couple of times I've accidentally run a golang program with
> libxl functionality on a system that wasn't running Xen (i.e., I'd
> rebooted onto Linux baremetal). Instead of throwing an error, as you
> would expect, it crashed with a SEGV.
>
> Try to reproduce this bug, and see if you can fix it.
>
> * If you want to dive into the project:
>
> I can send you my most recent version of libxl.go (which has a few
> more things implemented). Modify it so that it builds as a package (I
> think "xenproject.org/xenlight" is probably the best name), and wire
> it into the build system in tools/golang/xenlight, and installs into
> $prefix/share/gocode/src/xenproject.org/.
>
> The key thing with the last one is not to get too bogged down in
> systems you're not familiar with -- if you get stuck ask for help
> relatively quickly; and if it's turning into a mess, I can just do the
> Makefile side of things so that you can get to the actual Go side of
> the project.
>
> What do you think?
I think I would prefer to do the first task and then the last task. I
have not used stgit so I think it would be beneficial to do that first
and then I can dive into the project.
I will probably do the first task on either Sunday or Monday, depending
on when I can start working on it. The packaging task seems much more
difficult and I really only have a significant amount of time to work
on this during the weekend, so it'll probably take 1 or 2 more weeks
to complete that.
In the meantime I think it would be helpful to look at the makefile
of another subproject from xen so I could get some inspiration on how
structure this new project. Is there any Makefile that you think I
should look at? If not I'll just read through a couple of files in xen
and try to follow a similar style.
Does that sound like a good plan?
Ronald Rojas
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-10-06 14:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-14 6:35 New Outreachy Applicant Ronald Rojas
2016-09-20 15:24 ` George Dunlap
2016-10-03 5:14 ` Ronald Rojas
2016-10-04 14:23 ` George Dunlap
2016-10-05 17:44 ` George Dunlap
2016-10-06 14:26 ` Ronald Rojas [this message]
2016-10-06 15:16 ` George Dunlap
2016-10-07 10:15 ` George Dunlap
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20161006142627.GA6830@fedora \
--to=ronladred@gmail.com \
--cc=george.dunlap@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.