[PATCH] tools: Mark ACPI SDTs as NVS in the PVH build path

2025-03-11 Thread Alejandro Vallejo
Commit cefeffc7e583 marked ACPI tables as NVS in the hvmloader path because SeaBIOS may otherwise just mark it as RAM. There is, however, yet another reason to do it even in the PVH path. Xen's incarnation of AML relies on having access to some ACPI tables (e.g: _STA of Processor objects relies on

Re: [PATCH] tools: Mark ACPI SDTs as NVS in the PVH build path

2025-03-11 Thread Jan Beulich
On 10.03.2025 16:25, Alejandro Vallejo wrote: > Commit cefeffc7e583 marked ACPI tables as NVS in the hvmloader path > because SeaBIOS may otherwise just mark it as RAM. There is, however, > yet another reason to do it even in the PVH path. Xen's incarnation of > AML relies on having access to some

Re: [PATCH] tools: Mark ACPI SDTs as NVS in the PVH build path

2025-03-11 Thread Jan Beulich
On 11.03.2025 10:17, Alejandro Vallejo wrote: > On Tue Mar 11, 2025 at 8:30 AM GMT, Jan Beulich wrote: >> On 10.03.2025 16:25, Alejandro Vallejo wrote: >>> Commit cefeffc7e583 marked ACPI tables as NVS in the hvmloader path >>> because SeaBIOS may otherwise just mark it as RAM. There is, however, >

Re: [PATCH] tools: Mark ACPI SDTs as NVS in the PVH build path

2025-03-11 Thread Alejandro Vallejo
On Tue Mar 11, 2025 at 8:30 AM GMT, Jan Beulich wrote: > On 10.03.2025 16:25, Alejandro Vallejo wrote: > > Commit cefeffc7e583 marked ACPI tables as NVS in the hvmloader path > > because SeaBIOS may otherwise just mark it as RAM. There is, however, > > yet another reason to do it even in the PVH pa