xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Methuku Karthik <kmeth@seas.upenn.edu>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Stefano@aporeto.com, xen-devel@lists.xenproject.org,
	Dario.faggioli@citrix.com, Meng Xu <xumengpanda@gmail.com>,
	Lars.kurt@citrix.com
Subject: [GSoc] GSoc Introduction : Xen on ARM: create multiple guests from device tree
Date: Mon, 27 Mar 2017 01:47:57 -0400	[thread overview]
Message-ID: <CAOnoakf6z_KT6rwz61CDBdwEn74YriWi-i3uGpyD38O57VOeWw@mail.gmail.com> (raw)


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

Hi Everyone,

My name is Karthik. I am a first year graduate student in Embedded Systems
at University of Pennsylvania. I am avid c, c++ and python programmer.I
have 4 years of work experience as Embedded Software developer at Airbus.

For the last four months ​I ​have been working as a research assistant ​in
PRECISE lab at the University of Pennsylvania​, ​helping Meng Xu​ (cc.ed)​
to evaluate ​the performance of the Xen's RTDS scheduler.

I'm interested in the following two projects. I'm happy to work on one of
them.
(1) Share a page in memory from the VM config file​.
(2)  Xen on ARM: create multiple guests from device tree.

I have experience in compiling Xen and installing it on ARM board(Nvidia
Jetson TK1). I'm also well equiped in using the xl tool to manage the VMs.

I noticed that I should contribute some bug fixes to be able to get the
ticket to the Xen GSoC.
Do you have some suggestions on how I should start?
Do you have a list of simple bugs that I can fix?

I'm very interested in the Xen Project. I want to become a Xen contributor
in the near future.

Thank you very much for your help!

Best,
Karthik

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

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

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

             reply	other threads:[~2017-03-27  5:48 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-27  5:47 Methuku Karthik [this message]
2017-03-27 23:43 ` [GSoc] GSoc Introduction : Xen on ARM: create multiple guests from device tree Stefano Stabellini
2017-03-28 17:38   ` Stefano Stabellini
2017-03-28 23:25     ` Methuku Karthik
2017-03-28 23:56       ` Stefano Stabellini
2017-03-29  0:12         ` Stefano Stabellini
2017-04-03 15:43           ` Methuku Karthik
2017-04-03 19:35             ` Stefano Stabellini
2017-04-03 19:56               ` Methuku Karthik
2017-04-03 21:19                 ` Stefano Stabellini
2017-04-03 21:35                   ` Julien Grall
2017-04-04 17:29                 ` Stefano Stabellini
2017-04-06 23:29                   ` Methuku Karthik
2017-04-07  9:11                     ` Wei Liu
2017-04-07 17:20                       ` Stefano Stabellini

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=CAOnoakf6z_KT6rwz61CDBdwEn74YriWi-i3uGpyD38O57VOeWw@mail.gmail.com \
    --to=kmeth@seas.upenn.edu \
    --cc=Dario.faggioli@citrix.com \
    --cc=Lars.kurt@citrix.com \
    --cc=Stefano@aporeto.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xumengpanda@gmail.com \
    /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 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).