From: Julien Grall <julien.grall@arm.com>
To: Jan Beulich <JBeulich@suse.com>, Tim Deegan <tim@xen.org>
Cc: sstabellini@kernel.org, Wei Liu <wei.liu2@citrix.com>,
George Dunlap <George.Dunlap@eu.citrix.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Ian Jackson <ian.jackson@eu.citrix.com>,
xen-devel@lists.xen.org
Subject: Re: [PATCH v2 01/16] xen/mm: Don't use _{g, m}fn for defining INVALID_{G, M}FN
Date: Mon, 26 Jun 2017 14:11:21 +0100 [thread overview]
Message-ID: <94ba61da-a519-eb7f-1338-be3fc42f4e74@arm.com> (raw)
In-Reply-To: <594CFBFC0200007800166299@prv-mh.provo.novell.com>
Hi,
On 23/06/17 10:31, Jan Beulich wrote:
>>>> On 23.06.17 at 11:24, <tim@xen.org> wrote:
>> At 03:18 -0600 on 23 Jun (1498187924), Jan Beulich wrote:
>> How about:
>> - keep INVALID_MFN as an inline function call for most uses;
>> - #define INVALID_MFN_INITIALIZER { ~0UL } for when we need a
>> real constant initializer aat file scope.
>
> I'd be fine with that as much as with the other model.
I will send a patch to revert 725039d39e "mm: don't use _{g,m}fn for
defining INVALID_{G,M}FN" and one to add INVALID_MFN_INITIALIZER.
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
next prev parent reply other threads:[~2017-06-26 13:11 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-19 16:57 [PATCH v2 00/16] xen/arm: Clean-up memory subsystems Julien Grall
2017-06-19 16:57 ` [PATCH v2 01/16] xen/mm: Don't use _{g, m}fn for defining INVALID_{G, M}FN Julien Grall
2017-06-20 7:32 ` Jan Beulich
2017-06-20 9:14 ` Tim Deegan
2017-06-20 9:36 ` Jan Beulich
2017-06-20 10:06 ` Tim Deegan
2017-06-20 10:32 ` Jan Beulich
2017-06-22 18:31 ` Julien Grall
2017-06-23 8:30 ` Jan Beulich
2017-06-23 8:41 ` Julien Grall
2017-06-23 8:58 ` Tim Deegan
2017-06-23 9:01 ` Julien Grall
2017-06-23 9:02 ` Tim Deegan
2017-06-23 9:09 ` Jan Beulich
2017-06-23 8:55 ` Julien Grall
2017-06-23 9:18 ` Jan Beulich
2017-06-23 9:24 ` Tim Deegan
2017-06-23 9:31 ` Jan Beulich
2017-06-26 13:11 ` Julien Grall [this message]
2017-06-19 16:57 ` [PATCH v2 02/16] xen/arm: setup: Remove bogus xenheap_mfn_end in setup_mm for arm64 Julien Grall
2017-06-22 0:03 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 03/16] xen/arm: mm: Use typesafe mfn for xenheap_mfn_* Julien Grall
2017-06-21 23:58 ` Stefano Stabellini
2017-06-22 0:27 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 04/16] xen/arm: p2m: Redefine mfn_to_page and page_to_mfn to use typesafe Julien Grall
2017-06-22 0:00 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 05/16] xen/arm: mm: Redefine virt_to_mfn to support typesafe Julien Grall
2017-06-22 0:01 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 06/16] xen/arm: domain_build: " Julien Grall
2017-06-19 16:57 ` [PATCH v2 07/16] xen/arm: alternative: " Julien Grall
2017-06-19 16:57 ` [PATCH v2 08/16] xen/arm: livepatch: " Julien Grall
2017-06-19 17:06 ` Konrad Rzeszutek Wilk
2017-06-19 16:57 ` [PATCH v2 09/16] xen/arm: create_xen_entries: Use typesafe MFN Julien Grall
2017-06-19 16:57 ` [PATCH v2 10/16] xen/arm: Move LPAE definition in a separate header Julien Grall
2017-06-19 16:57 ` [PATCH v2 11/16] xen/arm: lpae: Fix comments coding style Julien Grall
2017-06-22 0:04 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 12/16] xen/arm: p2m: Rename p2m_valid, p2m_table, p2m_mapping and p2m_is_superpage Julien Grall
2017-06-20 8:14 ` Andrew Cooper
2017-06-21 13:34 ` Julien Grall
2017-06-22 0:08 ` Stefano Stabellini
2017-06-22 0:09 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 13/16] xen/arm: p2m: Move lpae_* helpers in lpae.h Julien Grall
2017-06-22 0:10 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 14/16] xen/arm: mm: Use lpae_valid and lpae_table in create_xen_entries Julien Grall
2017-06-22 0:14 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 15/16] xen/arm: mm: Introduce temporary variable " Julien Grall
2017-06-22 0:17 ` Stefano Stabellini
2017-06-19 16:57 ` [PATCH v2 16/16] xen/arm: mm: Use __func__ rather than plain name in format string Julien Grall
2017-06-22 0:18 ` Stefano Stabellini
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=94ba61da-a519-eb7f-1338-be3fc42f4e74@arm.com \
--to=julien.grall@arm.com \
--cc=George.Dunlap@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=ian.jackson@eu.citrix.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).