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

> We can provide a crafted MADT that reflects the number of vCPUs available to > Dom0 at boot time, let Dom0 find the Processor objects in the ACPI namespace > and perform pCPU hotplug as it's been done until now. Then for Dom0 vCPU > hotplug we would need to use the hypercall interface as it's

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

On Fri, Dec 23, 2016 at 12:13:47PM -0500, Boris Ostrovsky wrote: > On 12/23/2016 11:02 AM, Konrad Rzeszutek Wilk wrote: > > On Fri, Dec 23, 2016 at 10:35:10AM -0500, Boris Ostrovsky wrote: > >> On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote: > But this still assumes that dom0 handles

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

>>> On 22.12.16 at 19:19, wrote: > On 12/22/2016 11:44 AM, Roger Pau Monne wrote: >> On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: >> On 22.12.16 at 17:17, wrote: On 12/22/2016 07:17 AM, Roger Pau Monne wrote: >

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

On 12/23/2016 11:02 AM, Konrad Rzeszutek Wilk wrote: > On Fri, Dec 23, 2016 at 10:35:10AM -0500, Boris Ostrovsky wrote: >> On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote: But this still assumes that dom0 handles ACPI event for a pCPUs as well, right? And I am not sure this can work.

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

On Fri, Dec 23, 2016 at 10:35:10AM -0500, Boris Ostrovsky wrote: > On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote: > >> But this still assumes that dom0 handles ACPI event for a pCPUs as well, > >> right? And I am not sure this can work. > >> > >> Actually, how do we hotplug pCPUs now? > >

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

On 12/23/2016 10:31 AM, Konrad Rzeszutek Wilk wrote: >> But this still assumes that dom0 handles ACPI event for a pCPUs as well, >> right? And I am not sure this can work. >> >> Actually, how do we hotplug pCPUs now? > xen-hptool Yes, but this has nothing to do with an actual pCPU being

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

> But this still assumes that dom0 handles ACPI event for a pCPUs as well, > right? And I am not sure this can work. > > Actually, how do we hotplug pCPUs now? xen-hptool ___ Xen-devel mailing list Xen-devel@lists.xen.org

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

On Fri, Dec 23, 2016 at 10:27:46AM +, Roger Pau Monne wrote: > On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote: > > On 12/22/2016 11:44 AM, Roger Pau Monne wrote: > > > On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: > > > On 22.12.16 at 17:17,

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

On 12/23/2016 05:27 AM, Roger Pau Monne wrote: > On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote: >> On 12/22/2016 11:44 AM, Roger Pau Monne wrote: >>> On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: >>> On 22.12.16 at 17:17, wrote:

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

On Thu, Dec 22, 2016 at 01:19:36PM -0500, Boris Ostrovsky wrote: > On 12/22/2016 11:44 AM, Roger Pau Monne wrote: > > On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: > > On 22.12.16 at 17:17, wrote: > >>> On 12/22/2016 07:17 AM, Roger Pau Monne wrote:

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

On 12/22/2016 11:44 AM, Roger Pau Monne wrote: > On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: > On 22.12.16 at 17:17, wrote: >>> On 12/22/2016 07:17 AM, Roger Pau Monne wrote: Maybe Boris has some ideas about how to do CPU hotplug for Dom0? >>>

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

On Thu, Dec 22, 2016 at 09:24:02AM -0700, Jan Beulich wrote: > >>> On 22.12.16 at 17:17, wrote: > > On 12/22/2016 07:17 AM, Roger Pau Monne wrote: > >> Maybe Boris has some ideas about how to do CPU hotplug for Dom0? > > > > Why would Xen need to be able to parse the

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

>>> On 22.12.16 at 17:17, wrote: > On 12/22/2016 07:17 AM, Roger Pau Monne wrote: >> Maybe Boris has some ideas about how to do CPU hotplug for Dom0? > > Why would Xen need to be able to parse the AML that is intended to be > executed by dom0? I'd think that all the

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

On 12/22/2016 07:17 AM, Roger Pau Monne wrote: > On Thu, Dec 22, 2016 at 04:03:12AM -0700, Jan Beulich wrote: > On 22.12.16 at 11:43, wrote: >>> On Wed, Dec 21, 2016 at 10:04:20AM -0700, Jan Beulich wrote: > Since Xen is the one that sets the local APIC address in

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

On Thu, Dec 22, 2016 at 04:03:12AM -0700, Jan Beulich wrote: > >>> On 22.12.16 at 11:43, wrote: > > On Wed, Dec 21, 2016 at 10:04:20AM -0700, Jan Beulich wrote: > >> > Since Xen is the one that sets the local APIC address in the MADT, and it > >> > always matches the

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

>>> On 22.12.16 at 11:43, wrote: > On Wed, Dec 21, 2016 at 10:04:20AM -0700, Jan Beulich wrote: >> I'm not convinced these table entries are tied to >255 CPUs - I'm >> seeing them on systems with far less. Hence I simply wonder what >> functionality we may miss to offer to

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

On Wed, Dec 21, 2016 at 10:04:20AM -0700, Jan Beulich wrote: > >>> On 21.12.16 at 17:32, wrote: > > On Mon, Dec 12, 2016 at 06:56:36AM -0700, Jan Beulich wrote: > >> >>> On 30.11.16 at 17:49, wrote: > >> > +static int __init hvm_setup_acpi_madt(struct

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

>>> On 21.12.16 at 17:32, wrote: > On Mon, Dec 12, 2016 at 06:56:36AM -0700, Jan Beulich wrote: >> >>> On 30.11.16 at 17:49, wrote: >> > +static int __init hvm_setup_acpi_madt(struct domain *d, paddr_t *addr) >> > +{ >> > +struct acpi_table_madt

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

On Mon, Dec 12, 2016 at 06:56:36AM -0700, Jan Beulich wrote: > >>> On 30.11.16 at 17:49, wrote: > > @@ -567,7 +573,7 @@ static __init void hvm_setup_e820(struct domain *d, > > unsigned long nr_pages) > > /* > > * Craft the e820 memory map for Dom0 based on the

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

>>> On 30.11.16 at 17:49, wrote: > @@ -567,7 +573,7 @@ static __init void hvm_setup_e820(struct domain *d, > unsigned long nr_pages) > /* > * Craft the e820 memory map for Dom0 based on the hardware e820 map. > */ > -d->arch.e820 = xzalloc_array(struct

[Xen-devel] [PATCH v4 14/14] xen/x86: setup PVHv2 Dom0 ACPI tables

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.