On Sat, 26 Jan 2013 16:26:07 +0100
Andreas Färber afaer...@suse.de wrote:
Am 21.01.2013 15:06, schrieb Igor Mammedov:
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear distinction between
Am 21.01.2013 15:06, schrieb Igor Mammedov:
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear distinction between built-in cpu model defaults that eventually
should go into clas_init() and extra
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear distinction between built-in cpu model defaults that eventually
should go into clas_init() and extra property setting which is done
after defaults are
On Thu, 17 Jan 2013 15:44:45 -0200
Eduardo Habkost ehabk...@redhat.com wrote:
On Thu, Jan 17, 2013 at 04:16:33PM +0100, Igor Mammedov wrote:
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear distinction between built-in cpu model defaults that eventually
should go into clas_init() and extra property setting which is done
after defaults are
On Thu, Jan 17, 2013 at 04:16:33PM +0100, Igor Mammedov wrote:
Move custom features parsing after built-in cpu_model defaults are set
and set custom features directly on CPU instance. That allows to make
clear distinction between built-in cpu model defaults that eventually
should go into
