From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>
Cc: Tim Deegan <tim@xen.org>, Wei Liu <wei.liu2@citrix.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Steve Capper <Steve.Capper@arm.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org, Jan Beulich <jbeulich@suse.com>
Subject: Re: [PATCH v3 4/8] xen: Use typesafe gfn in xenmem_add_to_physmap_one
Date: Thu, 23 Jun 2016 14:33:55 +0100 [thread overview]
Message-ID: <576BE543.7050801@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1606231403420.2575@sstabellini-ThinkPad-X260>
On 23/06/16 14:06, Stefano Stabellini wrote:
> On Thu, 23 Jun 2016, Julien Grall wrote:
>> On 23/06/16 11:20, Stefano Stabellini wrote:
>>> On Tue, 21 Jun 2016, Julien Grall wrote:
>>> I think there is a possible loss of information here: xen_pfn_t is
>>> always uint64_t on both ARM and ARM64, while gfn_t is unsigned long with
>>> its current definition. Or am I missing something?
>>>
>>> In fact, given that ARM supports LPAE, shouldn't gfn by defined as
>>> xen_pfn_t in terms of storage size (TYPE_SAFE(xen_pfn_t, gfn)) ?
>>
>> With LPAE, ARM32 supports up to 40-bit PA so the frame will be encoded on
>> 28-bit. So unsigned long is perfectly fine here.
>
> Somehow I have always assumed that the 40-bit limitation was just
> temporary. That ARM in the future will just increase that number up to
> 64-bit eventually.
>
> If you don't think there is any risk of that happening, then I am fine
> with this. We just have to keep in mind that many of the guest
> interfaces use xen_pfn_t, which has a different size on ARM.
Currently, Aarch32 supports up to 40-bit whilst Aarch64 supports up to
48-bit (even 52-bit with ARMv8.2). So this should be ok for now.
However, pretty much everywhere in Xen we assume that the frame number
is unsigned long (see mm.c, p2m.c,...). We would have much more work to
do than this small patch.
I would rather start to switch to gfn/mfn internally and keep the
underlying type as "unsigned long" until we effectively need 64-bit frame.
The main reason is 64-bit frame will result into a bigger binary for
ARM32 with no apparent reason (40-bit is hardcoded in
setup_virt_paging). Switching to gfn/mfn will allow us to uint64_t where
it will be required.
Regards,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-06-23 13:33 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 13:20 [PATCH v3 0/8] xen/arm: Use the typesafes gfn and mfn Julien Grall
2016-06-21 13:20 ` [PATCH v3 1/8] xen/arm: Rename gmfn_to_mfn to gfn_to_mfn and use gfn/mfn typesafe Julien Grall
2016-06-23 10:06 ` Stefano Stabellini
2016-06-21 13:20 ` [PATCH v3 2/8] xen/mm: Introduce a bunch of helpers for the typesafes mfn and gfn Julien Grall
2016-06-22 7:03 ` Jan Beulich
2016-06-21 13:20 ` [PATCH v3 3/8] xen: Use typesafe gfn/mfn in guest_physmap_* helpers Julien Grall
2016-06-23 10:11 ` Stefano Stabellini
2016-06-21 13:20 ` [PATCH v3 4/8] xen: Use typesafe gfn in xenmem_add_to_physmap_one Julien Grall
2016-06-23 10:20 ` Stefano Stabellini
2016-06-23 10:43 ` Julien Grall
2016-06-23 13:06 ` Stefano Stabellini
2016-06-23 13:33 ` Julien Grall [this message]
2016-06-23 13:41 ` Stefano Stabellini
2016-06-23 13:58 ` Stefano Stabellini
2016-06-21 13:20 ` [PATCH v3 5/8] xen/arm: Rename grant_table_gfpn into grant_table_gfn and use the typesafe gfn Julien Grall
2016-06-23 14:00 ` Stefano Stabellini
2016-06-21 13:20 ` [PATCH v3 6/8] xen: Use the typesafe mfn and gfn in map_mmio_regions Julien Grall
2016-06-23 14:05 ` Stefano Stabellini
2016-06-23 14:08 ` Julien Grall
2016-06-23 14:15 ` Stefano Stabellini
2016-06-23 14:58 ` Julien Grall
2016-06-21 13:20 ` [PATCH v3 7/8] xen/arm: Rework the interface of p2m_lookup and use typesafe gfn and mfn Julien Grall
2016-06-23 14:14 ` Stefano Stabellini
2016-06-24 13:58 ` Julien Grall
2016-06-24 14:03 ` Andrew Cooper
2016-06-21 13:20 ` [PATCH v3 8/8] xen/arm: p2m_cache_flush: Use the correct terminology and typesafe gfn 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=576BE543.7050801@arm.com \
--to=julien.grall@arm.com \
--cc=Steve.Capper@arm.com \
--cc=andrew.cooper3@citrix.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=sstabellini@kernel.org \
--cc=tim@xen.org \
--cc=wei.liu2@citrix.com \
--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).