xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Luca Miccio <lucmiccio@gmail.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
	Julien Grall <julien.grall@arm.com>
Cc: Stefano@aporeto.com, xen-devel@lists.xenproject.org,
	Dario.faggioli@citrix.com, Lars.kurt@citrix.com
Subject: [GSoC] Xen on ARM: create multiple guests from device tree
Date: Tue, 21 Mar 2017 20:09:57 +0100	[thread overview]
Message-ID: <58D17A85.5050709@gmail.com> (raw)


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

Hi,
I'm an undergraduate student from the Computer Science Bachelor's Degree
of the University of Modena and Reggio Emilia (Italy).

I'm very interested in the "Xen on ARM: create multiple guests from 
device tree"
project.
A year ago I started a project on the "Hikey" board with the Android 
operating
system in order to integrate BFQ - which is a proportional-share storage-I/O
scheduler - in it  improving the device performances. Now the project is 
still in
development and it is supervised by my professor which, also, told me 
about GSoC.
Since I studied the C language for a full year at university and I 
already had to deal
with kernel-stuffs, cross-compiling and so on, I chose this project.

Since I'm not very familiar with the "device tree" notion, I'm wondering 
if you could give me
some suggestions on where I could start from.

The first thing I will do is to install xen and start to familiarize 
with it.
Any advice regarding this project will be really appreciated.

Best regards,

Luca


[-- Attachment #1.2: Type: text/html, Size: 2234 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-21 19:10 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-21 19:09 Luca Miccio [this message]
2017-03-21 20:36 ` [GSoC] Xen on ARM: create multiple guests from device tree Stefano Stabellini
2017-03-22 19:45   ` Luca Miccio
2017-03-22 20:11     ` Julien Grall
2017-03-22 21:38       ` Stefano Stabellini
2017-03-23  0:01         ` Luca Miccio
2017-03-23  0:27           ` Stefano Stabellini
2017-03-23  0:32             ` Luca Miccio
2017-03-23  0:55               ` Stefano Stabellini
2017-03-23  2:23                 ` Luca Miccio
2017-03-23 14:49                   ` Julien Grall
2017-03-23 18:03                     ` Luca Miccio
2017-03-28 17:30                       ` Stefano Stabellini
2017-03-29  0:13                         ` Stefano Stabellini
2017-03-30 18:14                           ` Luca Miccio
2017-03-29  8:07                       ` Julien Grall
2017-03-23 18:07                   ` Stefano Stabellini
2017-03-23 14:42                 ` Julien Grall
  -- strict thread matches above, loose matches on Subject: below --
2018-02-04  6:53 [GSOC] " Denis Obrezkov
2018-02-04  7:25 ` Denis Obrezkov
2018-02-05 17:53 ` Stefano Stabellini
2018-02-05 22:00   ` Denis Obrezkov
2018-02-07  0:08     ` Stefano Stabellini
2018-02-08  8:27       ` Denis Obrezkov
2018-02-08 16:26         ` 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=58D17A85.5050709@gmail.com \
    --to=lucmiccio@gmail.com \
    --cc=Dario.faggioli@citrix.com \
    --cc=Lars.kurt@citrix.com \
    --cc=Stefano@aporeto.com \
    --cc=julien.grall@arm.com \
    --cc=sstabellini@kernel.org \
    --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 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).