All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Denis Obrezkov <denisobrezkov@gmail.com>
Cc: edgar.iglesias@xilinx.com, xen-devel@lists.xenproject.org,
	julien.grall@arm.com, Stefano Stabellini <sstabellini@kernel.org>,
	lars.kurth@citrix.com
Subject: Re: [GSOC] Xen on ARM: create multiple guests from device tree
Date: Thu, 8 Feb 2018 08:26:03 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.10.1802080824100.15787@sstabellini-ThinkPad-X260> (raw)
In-Reply-To: <CAGPpAzWQ6QLA8gm6F7zLwyQEsjf_KL-SqPe0Z=GQ+9bznQY+Og@mail.gmail.com>

On Thu, 8 Feb 2018, Denis Obrezkov wrote:
> > Good! Please compile Xen for ARM64 and try to boot Xen and Dom0 with it.
> > Once you have Xen and Dom0 up and running, you can try to create a small
> > guest and start that as well. It will help you setup your build and test
> > environments.
> >
> > To build Xen for ARM64, you can use native compilation inside the
> > qemu-system-aarch64 emulation, but it is slow. Otherwise you can use
> > chroot and qemu-aarch64-static (the qemu-user aarch64 target, statically
> > compiled). For example give a look at:
> >
> > https://wiki.debian.org/Arm64Qemu
> >
> >
> > The end goal of the project is to be able to boot two domains directly
> > from Xen. Typically, Xen boots Dom0, then only once Dom0 is fully up and
> > running, a second domain can be created and that is done via the Xen
> > tools (xl). However, it is not always necessary to wait until Dom0 is
> > fully booted before starting a second guest. In many embedded
> > environments, you only have two or three guests in total to deal with.
> > It would be better to create them all in parallel directly from Xen. It
> > would drastically shorten the boot time.
> >
> > Device tree is used to describe the hardware available on the platform.
> > It comes into play in this project because it is the best way to pass
> > the required information to Xen, so that Xen knows it needs to boot a
> > second guest in addition to Dom0.
> >
> > Before we start the main project though, we usually ask candidates to
> > send a patch to fix a small issue just to show that they managed to
> > setup a dev and test environment correctly. We'll come back with a list
> > of potential small issues to fix shortly.
> >
> >
> >> I have also proposed to make a port of xen for qemu-system-riscv (it
> >> should be ready in Q2.2018) to people from riscv but I haven't
> >> received any answer.Anyway, I would like to work with xen on embedded
> >> platforms.
> >
> > That would be awesome, but I don't think that a project like porting Xen
> > to riscv would fit in a GSoC project :-)
> Thanks, I will try to do it this weekend.
> 
> Though, I want to note, that I probably won't participate in GSoC if
> Google continue their discrimination payment policy. For example, last
> year I've made a port of RTEMS for RISC-V and received $3600. At the
> same time one of the RTEMS project participants did almost nothing and
> was expelled from the program before the final evaluation and
> received...$3600. That was unfair! Could you imagine what my fellow
> from India felt who made an excellent project and received only $2400.
> 
> P.S. Is xen-project going to participate in Outreachy?

Yes, Xen Project is participating in Outreachy, and this specific Xen on
ARM project will also be available there.

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

  reply	other threads:[~2018-02-08 16:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-04  6:53 [GSOC] Xen on ARM: create multiple guests from device tree 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-03-21 19:09 [GSoC] " Luca Miccio
2017-03-21 20:36 ` 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

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=alpine.DEB.2.10.1802080824100.15787@sstabellini-ThinkPad-X260 \
    --to=sstabellini@kernel.org \
    --cc=denisobrezkov@gmail.com \
    --cc=edgar.iglesias@xilinx.com \
    --cc=julien.grall@arm.com \
    --cc=lars.kurth@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.