Re: [libvirt] [PATCH v2 21/33] cpu: Use virCPUData.arch in cpuDecode

2017-02-22 Thread Jiri Denemark
On Tue, Feb 21, 2017 at 22:24:34 -0500, John Ferlan wrote: > > > On 02/15/2017 11:44 AM, Jiri Denemark wrote: > > virCPUDef.arch is not required to be filled in for guest CPU > > definitions. It doesn't make sense to artificially mandate it to be set > > when cpuDecode is called especially when

Re: [libvirt] [PATCH v2 21/33] cpu: Use virCPUData.arch in cpuDecode

2017-02-21 Thread John Ferlan
On 02/15/2017 11:44 AM, Jiri Denemark wrote: > virCPUDef.arch is not required to be filled in for guest CPU > definitions. It doesn't make sense to artificially mandate it to be set > when cpuDecode is called especially when virCPUData.arch passed to > cpuDecode already contains the

[libvirt] [PATCH v2 21/33] cpu: Use virCPUData.arch in cpuDecode

2017-02-15 Thread Jiri Denemark
virCPUDef.arch is not required to be filled in for guest CPU definitions. It doesn't make sense to artificially mandate it to be set when cpuDecode is called especially when virCPUData.arch passed to cpuDecode already contains the architecture. Signed-off-by: Jiri Denemark