From: Julien Grall <julien.grall@arm.com>
To: "Xia, Hongyan" <hongyax@amazon.com>,
"xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>
Cc: "sstabellini@kernel.org" <sstabellini@kernel.org>,
"Volodymyr_Babchuk@epam.com" <Volodymyr_Babchuk@epam.com>
Subject: Re: [Xen-devel] [[PATCH for-4.13]] xen/arm: mm: Allow generic xen page-tables helpers to be called early
Date: Wed, 16 Oct 2019 13:46:46 +0100 [thread overview]
Message-ID: <6175492e-7e15-4338-2aed-0b5eee494782@arm.com> (raw)
In-Reply-To: <0acfc39467986475acddea19da96b55f2468b8fe.camel@amazon.com>
Hi Hongyan,
On 11/10/2019 10:53, Xia, Hongyan wrote:
> Not commenting on the patch, but I had exactly the same problem when
> removing the direct map in x86. map_domain_page has to be usable
> without the direct map and even before alloc_boot_pages can be used (so
> that I can map the bootmem_regions_list, although I have made it
> statically allocated now).
>
> The direct map teardown series in the end introduces a persistent
> mapping infrastructure to map page tables which occupies a few fixmap
> entries, and avoid set_fixmap but instead modify the entries directly
> to avoid invocation loops. The result is that map_xen_pagetable and
> map_domain_page is usable from the very beginning of start_xen.
Would you mind to point to the patch adding the implementation on x86?
On arm32, we are not using a direct map. So we are using a per-cpu mapping (see
map_domain_page() implementation in arch/arm/mm.c).
On arm64, we are using the direct map so far. But we could use any of the two
solutions if needed.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2019-10-16 12:47 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 16:02 [Xen-devel] [[PATCH for-4.13]] xen/arm: mm: Allow generic xen page-tables helpers to be called early Julien Grall
2019-09-19 23:37 ` Stefano Stabellini
2019-09-20 9:44 ` Julien Grall
2019-09-20 15:16 ` Stefano Stabellini
2019-09-20 15:26 ` Julien Grall
2019-10-02 17:49 ` Julien Grall
2019-10-03 1:02 ` Stefano Stabellini
2019-10-07 20:35 ` Julien Grall
2019-10-08 0:18 ` Stefano Stabellini
2019-10-08 14:02 ` Julien Grall
2019-10-08 22:24 ` Stefano Stabellini
2019-10-10 16:56 ` Julien Grall
2019-10-11 0:32 ` Stefano Stabellini
2019-10-11 10:14 ` Julien Grall
2019-10-11 17:11 ` Stefano Stabellini
2019-10-11 17:51 ` Julien Grall
2019-10-11 19:01 ` Stefano Stabellini
2019-10-11 19:14 ` Julien Grall
2019-09-25 15:23 ` Julien Grall
2019-09-25 15:27 ` Jürgen Groß
2019-10-11 9:53 ` Xia, Hongyan
2019-10-16 12:46 ` Julien Grall [this message]
2019-10-16 13:16 ` Xia, Hongyan
2019-10-10 17:52 [Xen-devel] [PATCH for-4.13] " Julien Grall
2019-10-11 0:27 ` Stefano Stabellini
2019-10-11 13:06 ` Julien Grall
2019-10-11 13:33 ` 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=6175492e-7e15-4338-2aed-0b5eee494782@arm.com \
--to=julien.grall@arm.com \
--cc=Volodymyr_Babchuk@epam.com \
--cc=hongyax@amazon.com \
--cc=sstabellini@kernel.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.