Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-28 Thread Roger Pau Monné
On Thu, Feb 27, 2025 at 02:12:58PM +, Alejandro Vallejo wrote: > Hi, > > On Wed Feb 26, 2025 at 5:33 PM GMT, Roger Pau Monné wrote: > > On Wed, Feb 26, 2025 at 02:11:23PM +0100, Jan Beulich wrote: > > > On 18.02.2025 15:22, Alejandro Vallejo wrote: > > > > @@ -1621,6 +1624,14 @@ static int cf_

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-27 Thread Alejandro Vallejo
On Thu Feb 27, 2025 at 7:29 AM GMT, Jan Beulich wrote: > On 26.02.2025 18:33, Roger Pau Monné wrote: > > On Wed, Feb 26, 2025 at 02:11:23PM +0100, Jan Beulich wrote: > >> On 18.02.2025 15:22, Alejandro Vallejo wrote: > >>> Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and > >>> int

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-27 Thread Alejandro Vallejo
On Wed Feb 26, 2025 at 1:11 PM GMT, Jan Beulich wrote: > On 18.02.2025 15:22, Alejandro Vallejo wrote: > > Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and > > interferes with providing accurate topology information to the guest. > > > > Introduce a new x2apic_id field into hvm_h

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-27 Thread Alejandro Vallejo
Hi, On Wed Feb 26, 2025 at 5:33 PM GMT, Roger Pau Monné wrote: > On Wed, Feb 26, 2025 at 02:11:23PM +0100, Jan Beulich wrote: > > On 18.02.2025 15:22, Alejandro Vallejo wrote: > > > Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and > > > interferes with providing accurate topology

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-26 Thread Jan Beulich
On 26.02.2025 18:33, Roger Pau Monné wrote: > On Wed, Feb 26, 2025 at 02:11:23PM +0100, Jan Beulich wrote: >> On 18.02.2025 15:22, Alejandro Vallejo wrote: >>> Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and >>> interferes with providing accurate topology information to the guest

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-26 Thread Roger Pau Monné
On Wed, Feb 26, 2025 at 02:11:23PM +0100, Jan Beulich wrote: > On 18.02.2025 15:22, Alejandro Vallejo wrote: > > Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and > > interferes with providing accurate topology information to the guest. > > > > Introduce a new x2apic_id field into

Re: [PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-26 Thread Jan Beulich
On 18.02.2025 15:22, Alejandro Vallejo wrote: > Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and > interferes with providing accurate topology information to the guest. > > Introduce a new x2apic_id field into hvm_hw_lapic.  This is immutable > state from the guest's point of vie

[PATCH] x86/hvm: Add APIC IDs to the per-vLAPIC save area

2025-02-18 Thread Alejandro Vallejo
Today, Xen hardcodes apic_id = vcpu_id * 2, but this is unwise and interferes with providing accurate topology information to the guest. Introduce a new x2apic_id field into hvm_hw_lapic.  This is immutable state from the guest's point of view, but it will allow the toolstack to eventually configu