OpenXT is derived from upstream projects which include Xen, QEMU and Linux. There is cross-pollination among upstream projects via sharing, duplication and derivation of source code. Macros centralize the implementations of important, repeated, source code patterns. Macros implement a simple interface for developers, removing complexity from source code, while their implementations can be complicated.
e.g. Xen source code macro implementations may diverge from those that originated and are maintained in other communities, e.g. QEMU and Linux. Upstream Xen does not yet have a tailored and security supported default configuration for client/edge use cases.
Topic raised, Feb 2019: https://lists.gt.net/xen/devel/544613
v1 process patch, Mar 2019: https://lists.gt.net/xen/devel/552764
v2 process patch, May 2019: https://lists.gt.net/xen/devel/553545
v3 process patch, May 2019: https://lists.gt.net/xen/devel/553744
This ticket is for ongoing review of upstream changes in macros which may affect OpenXT, as changes occur in upstream projects, OpenXT and derivative projects.