Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-24 Thread Igor Mammedov
On Sat, 21 Jan 2023 16:37:26 +0100 Bernhard Beschow wrote: > On Fri, Jan 20, 2023 at 5:34 PM Igor Mammedov wrote: > > > On Thu, 19 Jan 2023 14:47:41 + > > Bernhard Beschow wrote: > > > > > Am 18. Januar 2023 14:59:05 UTC schrieb Igor Mammedov < > > imamm...@redhat.com>: > > > >On Tue,

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-21 Thread Bernhard Beschow
On Fri, Jan 20, 2023 at 5:34 PM Igor Mammedov wrote: > On Thu, 19 Jan 2023 14:47:41 + > Bernhard Beschow wrote: > > > Am 18. Januar 2023 14:59:05 UTC schrieb Igor Mammedov < > imamm...@redhat.com>: > > >On Tue, 17 Jan 2023 00:30:23 + > > >Bernhard Beschow wrote: > > > > > >> Am 16.

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-20 Thread Igor Mammedov
On Thu, 19 Jan 2023 14:47:41 + Bernhard Beschow wrote: > Am 18. Januar 2023 14:59:05 UTC schrieb Igor Mammedov : > >On Tue, 17 Jan 2023 00:30:23 + > >Bernhard Beschow wrote: > > > >> Am 16. Januar 2023 16:29:30 UTC schrieb Igor Mammedov > >> : > >> >On Mon, 16 Jan 2023 16:29:03

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-19 Thread Bernhard Beschow
Am 18. Januar 2023 14:59:05 UTC schrieb Igor Mammedov : >On Tue, 17 Jan 2023 00:30:23 + >Bernhard Beschow wrote: > >> Am 16. Januar 2023 16:29:30 UTC schrieb Igor Mammedov : >> >On Mon, 16 Jan 2023 16:29:03 +0100 >> >Bernhard Beschow wrote: >> > >> >> This class attribute was always set

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-18 Thread Igor Mammedov
On Tue, 17 Jan 2023 00:30:23 + Bernhard Beschow wrote: > Am 16. Januar 2023 16:29:30 UTC schrieb Igor Mammedov : > >On Mon, 16 Jan 2023 16:29:03 +0100 > >Bernhard Beschow wrote: > > > >> This class attribute was always set to pc_madt_cpu_entry(). > >> pc_madt_cpu_entry() is architecture

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-17 Thread Bernhard Beschow
On Tue, Jan 17, 2023 at 1:30 AM Bernhard Beschow wrote: > > > Am 16. Januar 2023 16:29:30 UTC schrieb Igor Mammedov >: > >On Mon, 16 Jan 2023 16:29:03 +0100 > >Bernhard Beschow wrote: > > > >> This class attribute was always set to pc_madt_cpu_entry(). > >> pc_madt_cpu_entry() is architecture

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-16 Thread Bernhard Beschow
Am 16. Januar 2023 16:29:30 UTC schrieb Igor Mammedov : >On Mon, 16 Jan 2023 16:29:03 +0100 >Bernhard Beschow wrote: > >> This class attribute was always set to pc_madt_cpu_entry(). >> pc_madt_cpu_entry() is architecture dependent and was assigned to the >> attribute even in architecture

Re: [PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-16 Thread Igor Mammedov
On Mon, 16 Jan 2023 16:29:03 +0100 Bernhard Beschow wrote: > This class attribute was always set to pc_madt_cpu_entry(). > pc_madt_cpu_entry() is architecture dependent and was assigned to the > attribute even in architecture agnostic code such as in hw/acpi/piix4.c > and hw/isa/lpc_ich9. Not

[PATCH v3 2/7] hw/acpi/acpi_dev_interface: Resolve AcpiDeviceIfClass::madt_cpu

2023-01-16 Thread Bernhard Beschow
This class attribute was always set to pc_madt_cpu_entry(). pc_madt_cpu_entry() is architecture dependent and was assigned to the attribute even in architecture agnostic code such as in hw/acpi/piix4.c and hw/isa/lpc_ich9. Not having to set madt_cpu there resolves the assumption that these device