[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH] x86/Xen: streamline (and fix) PV CPU enumeration


  • To: Jan Beulich <jbeulich@xxxxxxxx>, Juergen Gross <jgross@xxxxxxxx>
  • From: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>
  • Date: Wed, 2 Feb 2022 09:27:36 -0500
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=none; dmarc=none; dkim=none; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=Tx+QcyU2eQsx0hhVOn9OV1f95Rvuz1MJe7mrx1LcNw4=; b=kQ2HwD1cqdz7Ow4T82KLDEt0raXopISR1SmJcvb+GbBZLRM+qE4fJaBu2cWULgKHZs+OLqxLT1LbMexIge9DCIzrU5Kme0st3GoZdB6EVdnv7Ge0s/0RDSwqabbRThITAMK4r1cs/ZQhmOQadeVwLFWaMXASmZXfFNEEKhW1W2iK/zqpetONgYlhKfqh4dlyyb+3wDxyBrcZLLwmH7d1jOBFWTbXuHYSz8RaFzJbz8EbR73Gi6+R84wuf5C3OHsy8bw89WclEGHIXpVbZJ5pkOdgPMFu+HB9FEx0iN5DMb9TUNNUlcZwTxY1F0Tp6XY0jedA9CxMKZIUI5YbomEQhQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=biBCqjUv6RJXHRxQuGoVnXOhs/dSvkQxGO29g/nWzFzSyjxf3CRBk9U2EtLA7RC807+k3jHuTwVIVNXjdiP//cbPVGLy2+iyGD72iCKokSjTZZ1AWvgjAxqv9Sr8wbcOc1x3s4yNrlsCvapEVKIQX9JTzJng8NY+C70RGYoDkMo/slD5Qo6SwqXoratSL+lGH9LoCj8TrtjTkwHkMdn/jS24avNplh1yd98xvGKOCceFT62UC4qAXEWhqwHThIMvxLeOZCQGp8kXqYSTeJj2VZNC84rZJ5uAIMJssG1lWBzg4Ef9EAuIJrIVJcM2fKaDG06KijN1Kbvbt11KstGj4A==
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 02 Feb 2022 14:27:51 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 2/1/22 5:57 AM, Jan Beulich wrote:
This started out with me noticing that "dom0_max_vcpus=<N>" with <N>
larger than the number of physical CPUs reported through ACPI tables
would not bring up the "excess" vCPU-s. Addressing this is the primary
purpose of the change; CPU maps handling is being tidied only as far as
is necessary for the change here (with the effect of also avoiding the
setting up of too much per-CPU infrastructure, i.e. for CPUs which can
never come online).

Noticing that xen_fill_possible_map() is called way too early, whereas
xen_filter_cpu_maps() is called too late (after per-CPU areas were
already set up), and further observing that each of the functions serves
only one of Dom0 or DomU, it looked like it was better to simplify this.
Use the .get_smp_config hook instead, uniformly for Dom0 and DomU.
xen_fill_possible_map() can be dropped altogether, while
xen_filter_cpu_maps() is re-purposed but not otherwise changed.

Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
---
v2: Extend description.


That's been a while ;-)


Reviewed-by: Boris Ostrovsky <boris.ostrovsky@xxxxxxxxxx>




 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.