Re: [PATCH] svm/avic: Allow avic_vcpu_load logic to support host APIC ID 255

2019-05-09 Thread Suthikulpanit, Suravee
Alex, Actually, a second thought on this patch, I should have been using AVIC_PHYSICAL_ID_ENTRY_HOST_PHYSICAL_ID_MASK ---> On 5/9/19 12:39 PM, Suthikulpanit, Suravee wrote: > [CAUTION: External Email] > > Alex, > > On 5/7/19 9:16 AM, Graf, Alexander wrote: >> [CAUTION: External Email] >> >> On

Re: [PATCH] svm/avic: Allow avic_vcpu_load logic to support host APIC ID 255

2019-05-09 Thread Suthikulpanit, Suravee
Alex, On 5/7/19 9:16 AM, Graf, Alexander wrote: > [CAUTION: External Email] > > On 03.05.19 15:37, Suthikulpanit, Suravee wrote: >> Current logic does not allow VCPU to be loaded onto CPU with >> APIC ID 255. This should be allowed since the host physical APIC ID >> field in the AVIC Physical API

Re: [PATCH] svm/avic: Allow avic_vcpu_load logic to support host APIC ID 255

2019-05-07 Thread Graf, Alexander
On 03.05.19 15:37, Suthikulpanit, Suravee wrote: Current logic does not allow VCPU to be loaded onto CPU with APIC ID 255. This should be allowed since the host physical APIC ID field in the AVIC Physical APIC table entry is an 8-bit value, and APIC ID 255 is valid in system with x2APIC enabled.

[PATCH] svm/avic: Allow avic_vcpu_load logic to support host APIC ID 255

2019-05-03 Thread Suthikulpanit, Suravee
Current logic does not allow VCPU to be loaded onto CPU with APIC ID 255. This should be allowed since the host physical APIC ID field in the AVIC Physical APIC table entry is an 8-bit value, and APIC ID 255 is valid in system with x2APIC enabled. Instead, do not allow VCPU load if the host APIC I