Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-07 Thread Radim Krčmář
2016-12-07 13:03+0100, Paolo Bonzini: > On 02/12/2016 20:44, Radim Krčmář wrote: >> LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of >> VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, >> but there is no way to uniquely address it using xAPIC. >> >> Fro

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-07 Thread Paolo Bonzini
On 02/12/2016 20:44, Radim Krčmář wrote: > LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of > VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, > but there is no way to uniquely address it using xAPIC. > > From many possible options, we chose the one t

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-06 Thread Radim Krčmář
2016-12-06 10:37+0100, David Hildenbrand: >> I think the agreement is to embrace compatibility, so we pile new >> mistakes to hide known ones. >> (Rewriting the past requires far more power than accepting it: >> If we didn't force unfixed kernels out of existence, then userspace >> couldn't tell

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-06 Thread David Hildenbrand
I think the agreement is to embrace compatibility, so we pile new mistakes to hide known ones. (Rewriting the past requires far more power than accepting it: If we didn't force unfixed kernels out of existence, then userspace couldn't tell if hotplug up to high VCPU ID limit is supported.) I

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-05 Thread Radim Krčmář
2016-12-05 19:00+0100, David Hildenbrand: > Am 05.12.2016 um 17:02 schrieb Radim Krčmář: >> 2016-12-05 15:37+0100, David Hildenbrand: >> > Am 02.12.2016 um 20:44 schrieb Radim Krčmář: >> > > LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of >> > > VCPUs with high APIC ID, bec

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-05 Thread David Hildenbrand
Am 05.12.2016 um 17:02 schrieb Radim Krčmář: 2016-12-05 15:37+0100, David Hildenbrand: Am 02.12.2016 um 20:44 schrieb Radim Krčmář: LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, but there is no way

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-05 Thread Radim Krčmář
2016-12-05 15:37+0100, David Hildenbrand: > Am 02.12.2016 um 20:44 schrieb Radim Krčmář: >> LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of >> VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, >> but there is no way to uniquely address it using xAPIC. >>

Re: [PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-05 Thread David Hildenbrand
Am 02.12.2016 um 20:44 schrieb Radim Krčmář: LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, but there is no way to uniquely address it using xAPIC. From many possible options, we chose the one that al

[PATCH 4/4] KVM: x86: allow hotplug of VCPU with APIC ID over 0xff

2016-12-02 Thread Radim Krčmář
LAPIC after reset is in xAPIC mode, which poses a problem for hotplug of VCPUs with high APIC ID, because reset VCPU is waiting for INIT/SIPI, but there is no way to uniquely address it using xAPIC. >From many possible options, we chose the one that also works on real hardware: accepting interrupt