Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-27 Thread Jan Beulich
On 26.03.2024 23:08, Julien Grall wrote: > Hi Andrew, > > On 20/03/2024 14:39, Andrew Cooper wrote: >> On 20/03/2024 2:26 pm, Roger Pau Monné wrote: >>> On Wed, Mar 20, 2024 at 02:06:27PM +, Andrew Cooper wrote: On 20/03/2024 1:57 pm, Roger Pau Monne wrote: > There's no reason to

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-26 Thread Julien Grall
Hi Andrew, On 20/03/2024 14:39, Andrew Cooper wrote: On 20/03/2024 2:26 pm, Roger Pau Monné wrote: On Wed, Mar 20, 2024 at 02:06:27PM +, Andrew Cooper wrote: On 20/03/2024 1:57 pm, Roger Pau Monne wrote: There's no reason to force HVM guests to have a valid vcpu_info area when

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-25 Thread Jan Beulich
On 20.03.2024 14:57, Roger Pau Monne wrote: > There's no reason to force HVM guests to have a valid vcpu_info area when > initializing a vCPU, as the vCPU can also be brought online using the local > APIC, and on that path there's no requirement for vcpu_info to be setup ahead > of the bring up.

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Jan Beulich
On 21.03.2024 10:57, Roger Pau Monné wrote: > On Thu, Mar 21, 2024 at 10:17:25AM +0100, Jan Beulich wrote: >> On 21.03.2024 10:10, Roger Pau Monné wrote: >>> On Thu, Mar 21, 2024 at 09:07:10AM +0100, Jan Beulich wrote: On 20.03.2024 17:29, Roger Pau Monné wrote: > On Wed, Mar 20, 2024 at

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Roger Pau Monné
On Thu, Mar 21, 2024 at 10:17:25AM +0100, Jan Beulich wrote: > On 21.03.2024 10:10, Roger Pau Monné wrote: > > On Thu, Mar 21, 2024 at 09:07:10AM +0100, Jan Beulich wrote: > >> On 20.03.2024 17:29, Roger Pau Monné wrote: > >>> On Wed, Mar 20, 2024 at 04:09:33PM +0100, Jan Beulich wrote: > On

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Jan Beulich
On 21.03.2024 10:10, Roger Pau Monné wrote: > On Thu, Mar 21, 2024 at 09:07:10AM +0100, Jan Beulich wrote: >> On 20.03.2024 17:29, Roger Pau Monné wrote: >>> On Wed, Mar 20, 2024 at 04:09:33PM +0100, Jan Beulich wrote: On 20.03.2024 14:57, Roger Pau Monne wrote: > There's no reason to

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Roger Pau Monné
On Thu, Mar 21, 2024 at 09:07:10AM +0100, Jan Beulich wrote: > On 20.03.2024 17:29, Roger Pau Monné wrote: > > On Wed, Mar 20, 2024 at 04:09:33PM +0100, Jan Beulich wrote: > >> On 20.03.2024 14:57, Roger Pau Monne wrote: > >>> There's no reason to force HVM guests to have a valid vcpu_info area

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Jan Beulich
On 20.03.2024 17:29, Roger Pau Monné wrote: > On Wed, Mar 20, 2024 at 04:09:33PM +0100, Jan Beulich wrote: >> On 20.03.2024 14:57, Roger Pau Monne wrote: >>> There's no reason to force HVM guests to have a valid vcpu_info area when >>> initializing a vCPU, as the vCPU can also be brought online

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-21 Thread Jan Beulich
On 20.03.2024 16:20, Andrew Cooper wrote: > On 20/03/2024 3:09 pm, Jan Beulich wrote: >> On 20.03.2024 14:57, Roger Pau Monne wrote: >>> There's no reason to force HVM guests to have a valid vcpu_info area when >>> initializing a vCPU, as the vCPU can also be brought online using the local >>>

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Roger Pau Monné
On Wed, Mar 20, 2024 at 04:09:33PM +0100, Jan Beulich wrote: > On 20.03.2024 14:57, Roger Pau Monne wrote: > > There's no reason to force HVM guests to have a valid vcpu_info area when > > initializing a vCPU, as the vCPU can also be brought online using the local > > APIC, and on that path

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Andrew Cooper
On 20/03/2024 3:09 pm, Jan Beulich wrote: > On 20.03.2024 14:57, Roger Pau Monne wrote: >> There's no reason to force HVM guests to have a valid vcpu_info area when >> initializing a vCPU, as the vCPU can also be brought online using the local >> APIC, and on that path there's no requirement for

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Jan Beulich
On 20.03.2024 14:57, Roger Pau Monne wrote: > There's no reason to force HVM guests to have a valid vcpu_info area when > initializing a vCPU, as the vCPU can also be brought online using the local > APIC, and on that path there's no requirement for vcpu_info to be setup ahead > of the bring up.

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Jan Beulich
On 20.03.2024 15:06, Andrew Cooper wrote: > On 20/03/2024 1:57 pm, Roger Pau Monne wrote: >> There's no reason to force HVM guests to have a valid vcpu_info area when >> initializing a vCPU, as the vCPU can also be brought online using the local >> APIC, and on that path there's no requirement for

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Andrew Cooper
On 20/03/2024 2:26 pm, Roger Pau Monné wrote: > On Wed, Mar 20, 2024 at 02:06:27PM +, Andrew Cooper wrote: >> On 20/03/2024 1:57 pm, Roger Pau Monne wrote: >>> There's no reason to force HVM guests to have a valid vcpu_info area when >>> initializing a vCPU, as the vCPU can also be brought

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Roger Pau Monné
On Wed, Mar 20, 2024 at 02:06:27PM +, Andrew Cooper wrote: > On 20/03/2024 1:57 pm, Roger Pau Monne wrote: > > There's no reason to force HVM guests to have a valid vcpu_info area when > > initializing a vCPU, as the vCPU can also be brought online using the local > > APIC, and on that path

Re: [PATCH] x86/vcpu: relax VCPUOP_initialise restriction for non-PV vCPUs

2024-03-20 Thread Andrew Cooper
On 20/03/2024 1:57 pm, Roger Pau Monne wrote: > There's no reason to force HVM guests to have a valid vcpu_info area when > initializing a vCPU, as the vCPU can also be brought online using the local > APIC, and on that path there's no requirement for vcpu_info to be setup ahead > of the bring up.