Haren Myneni <ha...@linux.ibm.com> writes: > The coprocessor capabilities struct is used to get default and > QoS capabilities from the hypervisor during init, DLPAR event and > migration. So instead of allocating this struct for each event, > define global struct and reuse it, especially eliminate memory > allocation failure during migration.
Which allows the migration code to avoid adding an error path. I could go either way, but this approach seems fine to me assuming all users of the global object are guarded by an appropriate lock. Acked-by: Nathan Lynch <nath...@linux.ibm.com>