xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@arm.com>
To: Andre Przywara <andre.przywara@arm.com>,
	Mark Rutland <mark.rutland@arm.com>
Cc: Jean-Philippe Brucker <jean-philippe.brucker@arm.com>,
	xen-devel@lists.xenproject.org,
	linux-arm-kernel@lists.infradead.org,
	Christoffer Dall <christoffer.dall@linaro.org>,
	Ian Campbell <ijc@hellion.org.uk>
Subject: Re: [PATCH 0/4] boot-wrapper: arm64: Xen support
Date: Tue, 12 Jul 2016 11:31:34 +0100	[thread overview]
Message-ID: <5784C706.1040007__48460.0485222929$1468319578$gmane$org@arm.com> (raw)
In-Reply-To: <20160620150934.1729-1-andre.przywara@arm.com>

Hi Andre,

On 20/06/16 16:09, Andre Przywara wrote:
> These patches allow to include a Xen hypervisor binary into a boot-wrapper
> ELF file, so that a Foundation Platform or a Fast Model can boot a Xen
> system (including a Dom0 kernel).
> This has been floating around for a while, I just updated the patches
> to apply on the latest boot-wrapper tree. Also I increased Xen's load
> address to accomodate for Dom0 kernels bigger than 16 MB.
> For testing this just add: "--with-xen=/path/to/xen/xen/xen" to the
> ./configure command line and feed the resulting xen-system.axf file to
> the model.

Tested-by: Julien Grall <julien.grall@arm.com>

Regards,

> Cheers,
> Andre.
>
> Christoffer Dall (3):
>    Support for building in a Xen binary
>    Xen: Support adding DT nodes
>    Explicitly clean linux-system.axf and xen-system.axf
>
> Ian Campbell (1):
>    Xen: Select correct dom0 console
>
>   .gitignore    |  1 +
>   Makefile.am   | 38 +++++++++++++++++++++++++-------------
>   boot_common.c |  4 ++--
>   configure.ac  | 26 +++++++++++++++++++++++++-
>   model.lds.S   | 14 ++++++++++++++
>   5 files changed, 67 insertions(+), 16 deletions(-)
>

-- 
Julien Grall

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

  parent reply	other threads:[~2016-07-12 10:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20160620150934.1729-1-andre.przywara@arm.com>
2016-06-20 15:09 ` [PATCH 1/4] Support for building in a Xen binary Andre Przywara
2016-07-12 10:40   ` Julien Grall
2016-07-15 10:12     ` Christoffer Dall
2016-06-20 15:09 ` [PATCH 2/4] Xen: Support adding DT nodes Andre Przywara
2016-07-12 10:48   ` Julien Grall
2016-06-20 15:09 ` [PATCH 3/4] Xen: Select correct dom0 console Andre Przywara
2016-07-12 10:49   ` Julien Grall
2016-06-20 15:09 ` [PATCH 4/4] Explicitly clean linux-system.axf and xen-system.axf Andre Przywara
2016-07-12 10:58   ` Julien Grall
2016-07-12 10:31 ` Julien Grall [this message]
2016-08-16 18:01 ` [PATCH 0/4] boot-wrapper: arm64: Xen support Julien Grall
2016-06-20 15:09 Andre Przywara

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='5784C706.1040007__48460.0485222929$1468319578$gmane$org@arm.com' \
    --to=julien.grall@arm.com \
    --cc=andre.przywara@arm.com \
    --cc=christoffer.dall@linaro.org \
    --cc=ijc@hellion.org.uk \
    --cc=jean-philippe.brucker@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mark.rutland@arm.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 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).