On 10/23/2017 01:03 PM, Paul Durrant wrote: snip>> +/*
Nope, the build fails unless I pad it to an 8 byte boundary. This is also why I added padding to struct xen_dm_op_pin_memory_cacheattr...+ * XEN_DMOP_add_to_physmap : Sets the GPFNs at which a page range appears in + * the specified guest's pseudophysical address + * space. Identical to XENMEM_add_to_physmap with + * space == XENMAPSPACE_gmfn_range. + */ +#define XEN_DMOP_add_to_physmap 17 + +struct xen_dm_op_add_to_physmap { + uint16_t size; /* Number of GMFNs to process. */ + uint16_t pad0; + uint32_t pad1;I think you can lose pad1 by putting idx and gpfn above size rather than below (since IIRC we only need pad up to the next 4 byte boundary).
-- Ross Lagerwall _______________________________________________ Xen-devel mailing list Xen-devel@lists.xen.org https://lists.xen.org/xen-devel
