From: Julien Grall <julien.grall@linaro.org>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: ian.jackson@eu.citrix.com, stefano.stabellini@eu.citrix.com,
tim@xen.org, xen-devel@lists.xen.org
Subject: Re: [PATCH v3 08/14] xen: arm: define guest virtual platform in API headers
Date: Mon, 11 Nov 2013 14:25:30 +0000 [thread overview]
Message-ID: <5280E8DA.1080506@linaro.org> (raw)
In-Reply-To: <1383904100.3189.52.camel@kazak.uk.xensource.com>
On 11/08/2013 09:48 AM, Ian Campbell wrote:
> On Thu, 2013-11-07 at 23:29 -0800, Julien Grall wrote:
>
>>> +#define PSR_THUMB (1<<5) /* Thumb Mode enable */
>>> +#define PSR_FIQ_MASK (1<<6) /* Fast Interrupt mask */
>>> +#define PSR_IRQ_MASK (1<<7) /* Interrupt mask */
>>> +#define PSR_ABT_MASK (1<<8) /* Asynchronous Abort mask */
>>> +#define PSR_BIG_ENDIAN (1<<9) /* Big Endian Mode */
>>> +#ifdef __aarch64__ /* For Aarch64 bit 9 is repurposed. */
>>
>> If you keep __aarch64__, you won't be able to have dom0 in 32 bits on arm64.
>
> Oops. I removed the others but missed this one. Nothing about this
> particular #if would prevent you having a 32 bit dom0 on arm64.
>
> But I'll remove the #define and add a comment anyway.
>
>> BTW, what does prevent the developer to use arm64 defines on arm64?
>
> Did you mean s/64/32/ in one of those? The answer is nothing other than
> code review, getting bug reports etc. I don't think there is any way we
> can prevent it programmatically. Maybe separate enums for 32 vs 64-bit
> PSR values, but I think that would get nasty fast.
What about defining arm64 specific stuff only if we are in xen tools or
in xen and build for arm64?
ie:
XEN_TOOLS || (XEN && ARM64)
>>
>>> +#define PSR_DBG_MASK (1<<9)
>>> +#endif
>>> +#define PSR_IT_MASK (0x0600fc00) /* Thumb If-Then Mask */
>>> +#define PSR_JAZELLE (1<<24) /* Jazelle Mode */
>>> +
>>> /* 32 bit modes */
>>> #define PSR_MODE_USR 0x10
>>> #define PSR_MODE_FIQ 0x11
>>> @@ -281,8 +294,6 @@ typedef uint64_t xen_callback_t;
>>> #define PSR_MODE_UND 0x1b
>>> #define PSR_MODE_SYS 0x1f
>>>
>>> -/* 64 bit modes */
>>
>> I would keep this commit. It's good to know that it's ARM64 specific.
>
> Yes.
>
>>
>>> -#ifdef __aarch64__
>>> #define PSR_MODE_BIT 0x10 /* Set iff AArch32 */
>>> #define PSR_MODE_EL3h 0x0d
>>> #define PSR_MODE_EL3t 0x0c
>>> @@ -291,18 +302,43 @@ typedef uint64_t xen_callback_t;
>>> #define PSR_MODE_EL1h 0x05
>>> #define PSR_MODE_EL1t 0x04
>>> #define PSR_MODE_EL0t 0x00
>>> -#endif
>>>
>>> -#define PSR_THUMB (1<<5) /* Thumb Mode enable */
>>> -#define PSR_FIQ_MASK (1<<6) /* Fast Interrupt mask */
>>> -#define PSR_IRQ_MASK (1<<7) /* Interrupt mask */
>>> -#define PSR_ABT_MASK (1<<8) /* Asynchronous Abort mask */
>>> -#define PSR_BIG_ENDIAN (1<<9) /* Big Endian Mode */
>>> -#ifdef __aarch64__ /* For Aarch64 bit 9 is repurposed. */
>>> -#define PSR_DBG_MASK (1<<9)
>>> +#define PSR_GUEST64_INIT (PSR_ABT_MASK|PSR_FIQ_MASK|PSR_IRQ_MASK|PSR_MODE_EL1h)
>>> +
>>> +#define SCTLR_GUEST_INIT 0x00c50078
>>> +
>>> +/*
>>> + * Virtual machine platform (memory layout, interrupts)
>>> + *
>>> + * These are defined for consistency between the tools and the
>>> + * hypervisor. Guests must not rely on these hardcoded values but
>>> + * should instead use the FDT.
>>> + */
>>> +
>>
>> I don't like the solution to hardcode GIC, IRQs (timer + evtchn) in the
>> public interface.
>
> Note that this is inside
> #if defined(__XEN__) || defined(__XEN_TOOLS__)
> so it is not exposed to guests and therefore not part of the guest ABI.
> The tools ABI is completely fungible and we can change it at will.
>
>> If we keep this solution, we will need to modify,
>> again, the ABI for ARM, why can't we add/extend some hypercalls to give
>> theses values to the hypervisor?
>
> That would be overkill until (if!) we get to the point of needing a more
> dynamic guest layout.
The current solution has some memory limitations. The layout doesn't
allow to allocate more than 768MB (space between the GUEST_RAM_BASE and
GUEST_GNTTAB_BASE).
>
> I'm not going to implement that now. I thought I'd expressed this in the
> commit message or the cover letter but it seems I forgot. I'll add some
> words to the commit message for the next posting.
Ok. Can you document somewhere the guest memory layout?
--
Julien Grall
next prev parent reply other threads:[~2013-11-11 14:25 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 16:44 [PATCH v3 00/14] xen: arm: 64-bit guest support and domU FDT autogeneration Ian Campbell
2013-11-07 16:44 ` [PATCH v3 01/14] xen: arm: Report aarch64 capability Ian Campbell
2013-11-07 16:44 ` [PATCH v3 02/14] xen: arm: Add comment regard arm64 zImage v0 vs v1 Ian Campbell
2013-11-07 16:44 ` [PATCH v3 03/14] xen: arm: allocate dom0 memory separately from preparing the dtb Ian Campbell
2013-11-08 7:18 ` Julien Grall
2013-11-08 9:36 ` Ian Campbell
2013-11-11 12:08 ` Julien Grall
2013-11-11 12:12 ` Ian Campbell
2013-11-11 12:25 ` Julien Grall
2013-11-11 13:17 ` Stefano Stabellini
2013-11-07 16:44 ` [PATCH v3 04/14] xen: arm: add enable-method to cpu nodes for arm64 guests Ian Campbell
2013-11-07 16:44 ` [PATCH v3 05/14] xen: arm: implement XEN_DOMCTL_set_address_size Ian Campbell
2013-11-11 12:13 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 06/14] xen: arm: implement arch_set_info_guest for 64-bit vcpus Ian Campbell
2013-11-08 7:20 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 07/14] tools: check for libfdt when building for ARM Ian Campbell
2013-11-07 17:04 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 08/14] xen: arm: define guest virtual platform in API headers Ian Campbell
2013-11-08 7:29 ` Julien Grall
2013-11-08 9:48 ` Ian Campbell
2013-11-11 14:25 ` Julien Grall [this message]
2013-11-11 15:12 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 09/14] libxc: arm: rename various bits of zimage load with 32 suffix Ian Campbell
2013-11-07 16:44 ` [PATCH v3 10/14] libxc: allow caller to specify guest rambase rather than hardcoding Ian Campbell
2013-11-07 17:06 ` Ian Jackson
2013-11-07 17:09 ` Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 16:44 ` [PATCH v3 11/14] libxc: allow passing a device tree blob to the guest Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-07 17:10 ` Ian Campbell
2013-11-07 17:31 ` Ian Jackson
2013-11-07 17:42 ` Ian Campbell
2013-11-12 10:46 ` Ian Campbell
2013-11-07 16:44 ` [PATCH v3 12/14] libxc: support for arm64 Image format Ian Campbell
2013-11-11 14:28 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 13/14] libxc: arm64 vcpu initialisation Ian Campbell
2013-11-07 17:09 ` Ian Jackson
2013-11-11 15:03 ` Julien Grall
2013-11-07 16:44 ` [PATCH v3 14/14] libxl: build a device tree for ARM guests Ian Campbell
2013-11-07 17:30 ` Ian Jackson
2013-11-07 17:41 ` Ian Campbell
2013-11-07 17:47 ` Ian Jackson
2013-11-08 9:30 ` Ian Campbell
2013-11-08 15:14 ` Ian Jackson
2013-11-11 12:14 ` Ian Campbell
2013-11-12 10:51 ` 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=5280E8DA.1080506@linaro.org \
--to=julien.grall@linaro.org \
--cc=Ian.Campbell@citrix.com \
--cc=ian.jackson@eu.citrix.com \
--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 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.