All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Orzel <michal.orzel@amd.com>
To: Julien Grall <julien@xen.org>, <xen-devel@lists.xenproject.org>
Cc: <Luca.Fancellu@arm.com>, <Henry.Wang@arm.com>,
	Julien Grall <jgrall@amazon.com>
Subject: Re: [v2 1/4] xen/arm64: head: Don't map too much in boot_third
Date: Fri, 30 Jun 2023 08:50:22 +0200	[thread overview]
Message-ID: <ad88adc9-5b05-65f9-2071-c746748ec3df@amd.com> (raw)
In-Reply-To: <20230629201129.12934-2-julien@xen.org>



On 29/06/2023 22:11, Julien Grall wrote:
> 
> 
> From: Julien Grall <jgrall@amazon.com>
> 
> At the moment, we are mapping the size of the reserved area for Xen
> (i.e. 2MB) even if the binary is smaller. We don't exactly know what's
> after Xen, so it is not a good idea to map more than necessary for a
> couple of reasons:
>     * We would need to use break-before-make if the extra PTE needs to
>       be updated to point to another region
>     * The extra area mapped may be mapped again by Xen with different
>       memory attribute. This would result to attribute mismatch.
> 
> Therefore, rework the logic in create_page_tables() to map only what's
> necessary. To simplify the logic, we also want to make sure _end
> is page-aligned. So align the symbol in the linker and add an assert
> to catch any change.
> 
> Lastly, take the opportunity to confirm that _start is equal to
> XEN_VIRT_START as the assembly is using both interchangeably.
> 
> Signed-off-by: Julien Grall <jgrall@amazon.com>
NIT: it looks like other maintainers are not CCed on this series.

Reviewed-by: Michal Orzel <michal.orzel@amd.com>

~Michal


  parent reply	other threads:[~2023-06-30  6:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29 20:11 [v2 0/4] xen/arm: Enable USBAN support Julien Grall
2023-06-29 20:11 ` [v2 1/4] xen/arm64: head: Don't map too much in boot_third Julien Grall
2023-06-29 22:52   ` Henry Wang
2023-06-30  6:50   ` Michal Orzel [this message]
2023-07-04 18:25     ` Julien Grall
2023-07-04 14:09   ` Bertrand Marquis
2023-06-29 20:11 ` [v2 2/4] xen/arm32: " Julien Grall
2023-06-29 22:53   ` Henry Wang
2023-07-04 14:12   ` Bertrand Marquis
2023-07-04 18:27     ` Julien Grall
2023-06-29 20:11 ` [v2 3/4] xen/arm: Rework the code mapping Xen to avoid relying on the size of Xen Julien Grall
2023-06-30  6:56   ` Michal Orzel
2023-07-04 18:28     ` Julien Grall
2023-07-04 14:23   ` Bertrand Marquis
2023-06-29 20:11 ` [v2 4/4] xen/arm: Allow the user to build Xen with UBSAN Julien Grall
2023-06-29 22:53   ` Henry Wang
2023-06-30  6:58   ` Michal Orzel
2023-07-04 18:30     ` Julien Grall
2023-07-04 14:14   ` Bertrand Marquis
2023-07-04 18:32 ` [v2 0/4] xen/arm: Enable USBAN support 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=ad88adc9-5b05-65f9-2071-c746748ec3df@amd.com \
    --to=michal.orzel@amd.com \
    --cc=Henry.Wang@arm.com \
    --cc=Luca.Fancellu@arm.com \
    --cc=jgrall@amazon.com \
    --cc=julien@xen.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 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.