Hi,

On 23/06/17 10:31, Jan Beulich wrote:
On 23.06.17 at 11:24, <t...@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

Reply via email to