From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>
Cc: julien.grall@linaro.org, tim@xen.org,
stefano.stabellini@eu.citrix.com, xen-devel@lists.xen.org
Subject: Re: [PATCH v6 10/16] xen: arm: define guest virtual platform in API headers
Date: Tue, 19 Nov 2013 17:58:17 +0000 [thread overview]
Message-ID: <528BA6B9.4010302@citrix.com> (raw)
In-Reply-To: <1384866024-13108-10-git-send-email-ian.campbell@citrix.com>
On 11/19/2013 01:00 PM, Ian Campbell wrote:
> The tools and the hypervisor need to agree on various aspects of the guest
> environment, such as interrupt numbers, memory layout, initial register values
> for registers which are implementation defined etc. Therefore move the
> associated defines into the public interface headers, or create them as
> necessary.
>
> This just exposes the current de-facto standard guest layout, which may be
> subject to change in the future. This deliberately does not make the guest
> layout dynamic since there is currently no need.
>
> These values should not be exposed to guests, they should find these things
> out via device tree or should not be relying on implementation defined
> defaults.
>
> Various bits of the hypervisor needed to change to configure dom0 with the real
> platform values while using the virtual platform configuration for guests.
> Arrange for this where appropriate and plumb through as needed.
>
> We also need to expose some 64-bit values (e.g. PSR_GUEST64_INIT) for the
> benefit of 32 bit toolstacks building 64 bit guests.
>
> Signed-off-by: Ian Campbell <ian.campbell@citrix.com>
> Acked-by: Stefano Stabellini <stefano.stabellini@eu.citrix.com>
> Acked-by: Julien Grall <julien.grall@linaro.org>
Hi,
I have just noticed that this patch breaks dom0 boot on most of ARM
platform. I have sent a separate patch to fix this issue. See:
https://patches.linaro.org/21632/
Cheers,
--
Julien Grall
next prev parent reply other threads:[~2013-11-19 17:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-19 12:59 [PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-19 13:00 ` [PATCH v6 01/16] xen: arm: Report aarch64 capability Ian Campbell
2013-11-19 13:00 ` [PATCH v6 02/16] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-19 13:00 ` [PATCH v6 03/16] xen: arm: move dom0 gic and timer device tree nodes under /xen-core-devices/ Ian Campbell
2013-11-19 14:05 ` Stefano Stabellini
2013-11-19 16:29 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 04/16] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-19 16:32 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 05/16] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-19 13:00 ` [PATCH v6 06/16] xen: arm: include header for for arch_do_{sys, dom}ctl prototype Ian Campbell
2013-11-19 13:00 ` [PATCH v6 07/16] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-19 13:00 ` [PATCH v6 08/16] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-19 13:00 ` [PATCH v6 09/16] tools: check for libfdt when building for ARM Ian Campbell
2013-11-19 13:00 ` [PATCH v6 10/16] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-19 17:58 ` Julien Grall [this message]
2013-11-19 13:00 ` [PATCH v6 11/16] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-19 13:00 ` [PATCH v6 12/16] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-19 13:00 ` [PATCH v6 13/16] libxc: arm: allow passing a device tree blob to the guest Ian Campbell
2013-11-19 16:34 ` Julien Grall
2013-11-19 13:00 ` [PATCH v6 14/16] libxc: support for arm64 Image format Ian Campbell
2013-11-19 13:00 ` [PATCH v6 15/16] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-19 13:00 ` [PATCH v6 16/16] libxl: build a device tree for ARM guests Ian Campbell
2013-11-19 15:45 ` [PATCH v6 00/16] xen: arm: 64-bit guest support and domU FDT autogeneration George Dunlap
2013-11-19 16:42 ` Ian Campbell
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=528BA6B9.4010302@citrix.com \
--to=julien.grall@citrix.com \
--cc=ian.campbell@citrix.com \
--cc=julien.grall@linaro.org \
--cc=stefano.stabellini@eu.citrix.com \
--cc=tim@xen.org \
--cc=xen-devel@lists.xen.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).