From: Andrew Cooper <andrew.cooper3@citrix.com>
To: Julien Grall <julien.grall@arm.com>, xen-devel@lists.xen.org
Cc: Elena Ufimtseva <elena.ufimtseva@oracle.com>,
Kevin Tian <kevin.tian@intel.com>,
sstabellini@kernel.org, Feng Wu <feng.wu@intel.com>,
Jan Beulich <jbeulich@suse.com>,
George Dunlap <george.dunlap@eu.citrix.com>,
Tim Deegan <tim@xen.org>, Christoph Egger <chegger@amazon.de>,
Ian Jackson <ian.jackson@eu.citrix.com>,
Paul Durrant <paul.durrant@citrix.com>,
Shannon Zhao <shannon.zhao@linaro.org>,
Jun Nakajima <jun.nakajima@intel.com>,
Liu Jinsong <jinsong.liu@alibaba-inc.com>,
Wei Liu <wei.liu2@citrix.com>,
Boris Ostrovsky <boris.ostrovsky@oracle.com>,
Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>
Subject: Re: [PATCH v7 00/14] xen/arm: Use the typesafes gfn and mfn
Date: Wed, 13 Jul 2016 14:13:37 +0100 [thread overview]
Message-ID: <205c5cb4-d864-686b-a0ad-e48c44ccad98@citrix.com> (raw)
In-Reply-To: <1468331975-27331-1-git-send-email-julien.grall@arm.com>
On 12/07/16 14:59, Julien Grall wrote:
> Hello all,
>
> Some of the ARM functions are mixing gfn vs mfn and even physical vs frame.
>
> To avoid more confusion, this patch series makes use of the terminology
> described in xen/include/xen/mm.h and the associated typesafe.
>
> I pushed a branch with this series applied on top of staging:
> git://xenbits.xen.org/people/julieng/xen-unstable.git branch typesafe-v7
Patches 1-6 committed.
~Andrew
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
prev parent reply other threads:[~2016-07-13 13:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-12 13:59 [PATCH v7 00/14] xen/arm: Use the typesafes gfn and mfn Julien Grall
2016-07-12 13:59 ` [PATCH v7 01/14] xen: Use the typesafe mfn and gfn in map_mmio_regions Julien Grall
2016-07-12 16:45 ` George Dunlap
2016-07-12 13:59 ` [PATCH v7 02/14] xen/passthrough: x86: Use INVALID_GFN rather than INVALID_MFN Julien Grall
2016-07-12 13:59 ` [PATCH v7 03/14] xen: Use a typesafe to define INVALID_MFN Julien Grall
2016-07-12 17:04 ` George Dunlap
2016-07-13 8:24 ` Tim Deegan
2016-07-13 0:11 ` Tian, Kevin
2016-07-12 13:59 ` [PATCH v7 04/14] xen: Use a typesafe to define INVALID_GFN Julien Grall
2016-07-12 17:12 ` George Dunlap
2016-07-13 0:13 ` Tian, Kevin
2016-07-12 13:59 ` [PATCH v7 05/14] xen/arm: Rework the interface of p2m_lookup and use typesafe gfn and mfn Julien Grall
2016-07-12 13:59 ` [PATCH v7 06/14] xen/arm: Rework the interface of p2m_cache_flush and use typesafe gfn Julien Grall
2016-07-12 13:59 ` [PATCH v7 07/14] xen/arm: map_regions_rw_cache: Map the region with p2m->default_access Julien Grall
2016-07-13 17:34 ` Stefano Stabellini
2016-07-12 13:59 ` [PATCH v7 08/14] xen/arm: dom0_build: Remove dead code in allocate_memory Julien Grall
2016-07-12 13:59 ` [PATCH v7 09/14] xen/arm: p2m: Remove unused operation ALLOCATE Julien Grall
2016-07-12 13:59 ` [PATCH v7 10/14] xen/arm: Use the typesafes mfn and gfn in map_dev_mmio_region Julien Grall
2016-07-13 17:37 ` Stefano Stabellini
2016-07-12 13:59 ` [PATCH v7 11/14] xen/arm: Use the typesafes mfn and gfn in map_regions_rw_cache Julien Grall
2016-07-12 13:59 ` [PATCH v7 12/14] xen/arm: p2m: Introduce helpers to insert and remove mapping Julien Grall
2016-07-13 17:51 ` Stefano Stabellini
2016-07-12 13:59 ` [PATCH v7 13/14] xen/arm: p2m: Use typesafe gfn for {max, lowest}_mapped_gfn Julien Grall
2016-07-12 13:59 ` [PATCH v7 14/14] xen/arm: p2m: Rework the interface of apply_p2m_changes and use typesafe Julien Grall
2016-07-13 17:50 ` Stefano Stabellini
2016-07-13 13:13 ` Andrew Cooper [this message]
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=205c5cb4-d864-686b-a0ad-e48c44ccad98@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=boris.ostrovsky@oracle.com \
--cc=chegger@amazon.de \
--cc=elena.ufimtseva@oracle.com \
--cc=feng.wu@intel.com \
--cc=george.dunlap@eu.citrix.com \
--cc=ian.jackson@eu.citrix.com \
--cc=jbeulich@suse.com \
--cc=jinsong.liu@alibaba-inc.com \
--cc=julien.grall@arm.com \
--cc=jun.nakajima@intel.com \
--cc=kevin.tian@intel.com \
--cc=paul.durrant@citrix.com \
--cc=shannon.zhao@linaro.org \
--cc=sstabellini@kernel.org \
--cc=suravee.suthikulpanit@amd.com \
--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).