Re: [Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-02-08 Thread Jan Beulich
>>> On 08.02.17 at 16:58, wrote: > On Wed, Feb 08, 2017 at 08:50:54AM -0700, Jan Beulich wrote: >> >>> On 08.02.17 at 16:10, wrote: >> > On Thu, Jan 26, 2017 at 07:16:32AM -0700, Jan Beulich wrote: >> >> >>> On 19.01.17 at 18:29, wrote: >> >> > +/* >> >> > + * The APIC ID field of the lo

Re: [Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-02-08 Thread Roger Pau Monne
On Wed, Feb 08, 2017 at 08:50:54AM -0700, Jan Beulich wrote: > >>> On 08.02.17 at 16:10, wrote: > > On Thu, Jan 26, 2017 at 07:16:32AM -0700, Jan Beulich wrote: > >> >>> On 19.01.17 at 18:29, wrote: > >> > +/* > >> > + * The APIC ID field of the local APIC struct is only 1byte, so we > >

Re: [Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-02-08 Thread Jan Beulich
>>> On 08.02.17 at 16:10, wrote: > On Thu, Jan 26, 2017 at 07:16:32AM -0700, Jan Beulich wrote: >> >>> On 19.01.17 at 18:29, wrote: >> > +/* >> > + * The APIC ID field of the local APIC struct is only 1byte, so we >> > need >> > + * to limit the number of local APIC entries to 128 be

Re: [Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-02-08 Thread Roger Pau Monne
On Thu, Jan 26, 2017 at 07:16:32AM -0700, Jan Beulich wrote: > >>> On 19.01.17 at 18:29, wrote: > > +static int __init pvh_setup_acpi_madt(struct domain *d, paddr_t *addr) > > +{ > > +struct acpi_table_madt *madt; > > +struct acpi_table_header *table; > > +struct acpi_madt_io_apic *io_

Re: [Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-01-26 Thread Jan Beulich
>>> On 19.01.17 at 18:29, wrote: > +static int __init pvh_setup_acpi_madt(struct domain *d, paddr_t *addr) > +{ > +struct acpi_table_madt *madt; > +struct acpi_table_header *table; > +struct acpi_madt_io_apic *io_apic; > +struct acpi_madt_local_apic *local_apic; > +struct acpi_

[Xen-devel] [PATCH v5 9/9] xen/x86: setup PVHv2 Dom0 ACPI tables

2017-01-19 Thread Roger Pau Monne
Create a new MADT table that contains the topology exposed to the guest. A new XSDT table is also created, in order to filter the tables that we want to expose to the guest, plus the Xen crafted MADT. This in turn requires Xen to also create a new RSDP in order to make it point to the custom XSDT.