[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Qemu-devel] [PATCH v2 3/3] i386: Don't set CPUClass::cpu_def on "ma
|
From: |
Eduardo Habkost |
|
Subject: |
Re: [Qemu-devel] [PATCH v2 3/3] i386: Don't set CPUClass::cpu_def on "max" model |
|
Date: |
Fri, 24 Feb 2017 09:33:08 -0300 |
|
User-agent: |
Mutt/1.7.1 (2016-10-04) |
On Fri, Feb 24, 2017 at 12:13:05PM +0100, David Hildenbrand wrote:
> Am 22.02.2017 um 19:39 schrieb Eduardo Habkost:
> > Host CPUID info is used by the "max" CPU model only in KVM mode.
> > Move the initialization of CPUID data for "max" from class_init
> > to instance_init, and don't set CPUClass::cpu_def for "max".
>
> Doesn't that mean that the same code is now called for every cpu
> instance vs. only once for the class?
Yes, but I don't see a problem with that.
--
Eduardo
[Qemu-devel] [PATCH v2 3/3] i386: Don't set CPUClass::cpu_def on "max" model, Eduardo Habkost, 2017/02/22
Re: [Qemu-devel] [PATCH v2 0/3] i386: Add "max" CPU model to TCG and KVM, Eduardo Habkost, 2017/02/23
Re: [Qemu-devel] [PATCH v2 0/3] i386: Add "max" CPU model to TCG and KVM, Peter Maydell, 2017/02/24