On Thu, Oct 26, 2017 at 12:24 PM +0200, Jiri Denemark
wrote:
> On Wed, Oct 25, 2017 at 10:56:51 +0200, Marc Hartmayer wrote:
>> On Fri, Oct 13, 2017 at 08:14 PM +0200, Jiri Denemark
>> wrote:
>> > When a hypervisor marks a CPU model as unusable on the
On Wed, Oct 25, 2017 at 10:56:51 +0200, Marc Hartmayer wrote:
> On Fri, Oct 13, 2017 at 08:14 PM +0200, Jiri Denemark
> wrote:
> > When a hypervisor marks a CPU model as unusable on the current host, it
> > may also give us a list of features which prevent the model from
On Wed, Oct 25, 2017 at 10:56 AM +0200, Marc Hartmayer
wrote:
> On Fri, Oct 13, 2017 at 08:14 PM +0200, Jiri Denemark
> wrote:
>> When a hypervisor marks a CPU model as unusable on the current host, it
>> may also give us a list of features
On Fri, Oct 13, 2017 at 08:14 PM +0200, Jiri Denemark
wrote:
> When a hypervisor marks a CPU model as unusable on the current host, it
> may also give us a list of features which prevent the model from being
> usable. Storing this list in virDomainCapsCPUModel will help the
When a hypervisor marks a CPU model as unusable on the current host, it
may also give us a list of features which prevent the model from being
usable. Storing this list in virDomainCapsCPUModel will help the CPU
driver with creating a host-model CPU configuration.
Signed-off-by: Jiri Denemark