RE: [PATCH RFC V2 22/37] hw/acpi: Make _MAT method optional

2023-10-16 Thread Salil Mehta via
.@loongson.cn; lixiang...@loongson.cn > Subject: Re: [PATCH RFC V2 22/37] hw/acpi: Make _MAT method optional > > On 9/26/23 20:04, Salil Mehta wrote: > > From: Jean-Philippe Brucker > > > > The GICC interface on arm64 vCPUs is statically defined in the MADT, and > >

Re: [PATCH RFC V2 22/37] hw/acpi: Make _MAT method optional

2023-09-28 Thread Gavin Shan
On 9/26/23 20:04, Salil Mehta wrote: From: Jean-Philippe Brucker The GICC interface on arm64 vCPUs is statically defined in the MADT, and doesn't require a _MAT entry. Although the GICC is indicated as present by the MADT entry, it can only be used from vCPU sysregs, which aren't accessible unt

[PATCH RFC V2 22/37] hw/acpi: Make _MAT method optional

2023-09-26 Thread Salil Mehta via
From: Jean-Philippe Brucker The GICC interface on arm64 vCPUs is statically defined in the MADT, and doesn't require a _MAT entry. Although the GICC is indicated as present by the MADT entry, it can only be used from vCPU sysregs, which aren't accessible until hot-add. Co-developed-by: Jean-Phil