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

Re: [PATCH v5] ACPI: processor: Fix evaluating _PDC method when running as Xen dom0


  • To: Juergen Gross <jgross@xxxxxxxx>
  • From: Roger Pau Monné <roger.pau@xxxxxxxxxx>
  • Date: Mon, 27 Mar 2023 17:49:07 +0200
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=citrix.com; dmarc=pass action=none header.from=citrix.com; dkim=pass header.d=citrix.com; 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=dFnXZhChO5CCthg+ZeSR3Ak6o6goOFLBpgEYERvumh0=; b=N1NlSgoV3Hop6TH5ALVvu2iZuS8BJF7SgLSNHj1YnvwC8wF73X4IB7rnQN/nVGgiK/0rnown3rw+fxboRM0MsxdhJ0LC/ExBFcIIROvqRCJmryfCTE9955hTP+Vyku4sBvogicrQvnTd/SkAjjB/BqcjW2EKFL8hwB/d0sD24Ua9jyop7keABzz7z07B9vj1bMDgLTEaP/BZc018eYxyY/CRfBdJ0LNgG8z51R7SCybie2skGzjHRH3ozBn/FmBLQ/9cpzz/rgFg0HTCrrIuQP9djaOrtkfH2Ll8tRL0IXjcIO9u71BcT9fbMAwhfOZHFZs4qjZlydmFWzHjOJi6UQ==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=C4fTL2Crh+gGyHa9CfGe8gOvdGeYICouSJV9AUBYAtF7sDACjIl1SwfAuPrVGRC1I/0uHmQi6UGyP1UIPVkvPK9Wiy2mX65mBg0QNg76Pee4UvWxU11+EnXVelp9O2IORE4IQagStHmO68MkWzYMoP9FUjhcMGI2jLw4K+4eqvVnQVzO+pz91h6hIydJXGB/kEWtAMcI9K1yJYsjp+4R58KTu41FGd0PSxWUy06V2cqYPIJefgIg4cIA8MbLEaDcBbJq2COfFojJb7DIzjf9yLMJgoI5WtSpDVxwf3yB+yKuRN3LWiFiYVJHq3K3ISLJOJH7n2fJ7KwnHPA2+RXAnw==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=citrix.com;
  • Cc: linux-kernel@xxxxxxxxxxxxxxx, Stefano Stabellini <sstabellini@xxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxx, "Rafael J. Wysocki" <rafael@xxxxxxxxxx>, Len Brown <lenb@xxxxxxxxxx>, Oleksandr Tyshchenko <oleksandr_tyshchenko@xxxxxxxx>, Venkatesh Pallipadi <venkatesh.pallipadi@xxxxxxxxx>, Alex Chiang <achiang@xxxxxx>, linux-acpi@xxxxxxxxxxxxxxx
  • Delivery-date: Mon, 27 Mar 2023 15:49:33 +0000
  • Ironport-data: A9a23:3ZEera6nb6UmbSuyxR1/2gxRtGTHchMFZxGqfqrLsTDasY5as4F+v jZNUDyFOKuJZWbzLo1yYIu+oU9Xv8LQyd41TAprpXs0Hi5G8cbLO4+Ufxz6V8+wwm8vb2o8t plDNYOQRCwQZiWBzvt4GuG59RGQ7YnRGvynTraCYnsrLeNdYH9JoQp5nOIkiZJfj9G8Agec0 fv/uMSaM1K+s9JOGjt8B5mr9VU+7JwehBtC5gZlPasR4weE/5UoJMl3yZ+ZfiOQrrZ8RoZWd 86bpJml82XQ+QsaC9/Nut4XpWVTH9Y+lSDX4pZnc/DKbipq/0Te4Y5iXBYoUm9Fii3hojxE4 I4lWapc6+seFvakdOw1C3G0GszlVEFM0OevzXOX6aR/w6BaGpdFLjoH4EweZOUlFuhL7W5my qMldhcKYy+63sGL/aOhZ8V+o5QaFZy+VG8fkikIITDxK98DGMmGaIKToNhS0XE3m9xEGuvYa 4wBcz1zYR/cYhpJfFAKFJY5m+TujX76G9FagAvN+exrvC6Okkooj+aF3Nn9I7RmQe1PmUmVv CTe9nnRCRAGLt2PjzGC9xpAg8eWxXinBNhCTubQGvhCg1iYmjw+Mi0qVlanr6CBqH65fIxiN BlBksYphe1onKCxdfH/UAe/u2WspQMHVpxbFOhSwAWMzLfEpgWUHG4JShZfZ9E88sw7Xzon0 hmOhdyBLSd0rLSfRHaZ97GVhTC/Iy4YKSkFfyBsZRsI5ZzvrZ8+ijrLT81/C+ilg9vtAzbyz juW6i8kiN07l8cF3qi/1VPKmTShot7OVAFdzgHaWGiN7Q5jYoOhIYuy5jDz6vJNL52QSFWbi 2QVgMiV7O0IDpalmTSERaMGG7TBz+iINj7VnVN0H985/jCp+maqcYF44TdiKUMvOcEBERfga 0/SsAVezJ9LenCtaMdfZ4O3FtRvxKP4FPz7Wf3OKNlDeJ58cEmA5i4GWKKL92XkkUxpmqZmP 56eKJ+oFSxDVvohyyeqTeAA17Nt3jo52W7YWZH8yVKgzKaaY3mWD7wCNTNic9wE0U9Nmy2Nm /43CidA4043vDHWCsUPzbMuEA==
  • Ironport-hdrordr: A9a23:+WkoOKGkL2hV385+pLqEL8eALOsnbusQ8zAXP0AYc20yTiX4ra CTdZEgviMc5wxxZJhNo6HkBEDiewKkyXcW2/hoAV7KZmCP1wWVxelZnPDfKlbbaknDH4BmpM BdWpk7JefcSX5dpq/BjDVQFexL/PC3tJqFv6P16VBDbS9XUIlczyFfTjy2LyRNNWp7LKt8G5 qY6tBGtDa7EE57Uu2wGmMZWezOvP3n/aiWAyI7Ow==
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>

On Mon, Mar 27, 2023 at 03:58:26PM +0200, Juergen Gross wrote:
> On 21.03.23 15:19, Roger Pau Monne wrote:
> > In ACPI systems, the OS can direct power management, as opposed to the
> > firmware.  This OS-directed Power Management is called OSPM.  Part of
> > telling the firmware that the OS going to direct power management is
> > making ACPI "_PDC" (Processor Driver Capabilities) calls.  These _PDC
> > methods must be evaluated for every processor object.  If these _PDC
> > calls are not completed for every processor it can lead to
> > inconsistency and later failures in things like the CPU frequency
> > driver.
> > 
> > In a Xen system, the dom0 kernel is responsible for system-wide power
> > management.  The dom0 kernel is in charge of OSPM.  However, the
> > number of CPUs available to dom0 can be different than the number of
> > CPUs physically present on the system.
> > 
> > This leads to a problem: the dom0 kernel needs to evaluate _PDC for
> > all the processors, but it can't always see them.
> > 
> > In dom0 kernels, ignore the existing ACPI method for determining if a
> > processor is physically present because it might not be accurate.
> > Instead, ask the hypervisor for this information.
> > 
> > Fix this by introducing a custom function to use when running as Xen
> > dom0 in order to check whether a processor object matches a CPU that's
> > online.  Such checking is done using the existing information fetched
> > by the Xen pCPU subsystem, extending it to also store the ACPI ID.
> > 
> > This ensures that _PDC method gets evaluated for all physically online
> > CPUs, regardless of the number of CPUs made available to dom0.
> > 
> > Fixes: 5d554a7bb064 ('ACPI: processor: add internal 
> > processor_physically_present()')
> > Signed-off-by: Roger Pau Monné <roger.pau@xxxxxxxxxx>
> > ---
> > Changes since v4:
> >   - Move definition/declaration of xen_processor_present() to different
> >     header.
> >   - Fold subject edit.
> > 
> > Changes since v3:
> >   - Protect xen_processor_present() definition with CONFIG_ACPI.
> > 
> > Changes since v2:
> >   - Extend and use the existing pcpu functionality.
> > 
> > Changes since v1:
> >   - Reword commit message.
> > ---
> >   drivers/acpi/processor_pdc.c | 11 +++++++++++
> >   drivers/xen/pcpu.c           | 20 ++++++++++++++++++++
> >   include/xen/xen.h            | 10 ++++++++++
> >   3 files changed, 41 insertions(+)
> > 
> > diff --git a/drivers/acpi/processor_pdc.c b/drivers/acpi/processor_pdc.c
> > index 8c3f82c9fff3..18fb04523f93 100644
> > --- a/drivers/acpi/processor_pdc.c
> > +++ b/drivers/acpi/processor_pdc.c
> > @@ -14,6 +14,8 @@
> >   #include <linux/acpi.h>
> >   #include <acpi/processor.h>
> > +#include <xen/xen.h>
> > +
> >   #include "internal.h"
> >   static bool __init processor_physically_present(acpi_handle handle)
> > @@ -47,6 +49,15 @@ static bool __init 
> > processor_physically_present(acpi_handle handle)
> >             return false;
> >     }
> > +   if (xen_initial_domain())
> > +           /*
> > +            * When running as a Xen dom0 the number of processors Linux
> > +            * sees can be different from the real number of processors on
> > +            * the system, and we still need to execute _PDC for all of
> > +            * them.
> > +            */
> > +           return xen_processor_present(acpi_id);
> > +
> >     type = (acpi_type == ACPI_TYPE_DEVICE) ? 1 : 0;
> >     cpuid = acpi_get_cpuid(handle, type, acpi_id);
> > diff --git a/drivers/xen/pcpu.c b/drivers/xen/pcpu.c
> > index fd3a644b0855..1814f8762f54 100644
> > --- a/drivers/xen/pcpu.c
> > +++ b/drivers/xen/pcpu.c
> > @@ -58,6 +58,7 @@ struct pcpu {
> >     struct list_head list;
> >     struct device dev;
> >     uint32_t cpu_id;
> > +   uint32_t acpi_id;
> >     uint32_t flags;
> >   };
> > @@ -249,6 +250,7 @@ static struct pcpu *create_and_register_pcpu(struct 
> > xenpf_pcpuinfo *info)
> >     INIT_LIST_HEAD(&pcpu->list);
> >     pcpu->cpu_id = info->xen_cpuid;
> > +   pcpu->acpi_id = info->acpi_id;
> >     pcpu->flags = info->flags;
> >     /* Need hold on xen_pcpu_lock before pcpu list manipulations */
> > @@ -381,3 +383,21 @@ static int __init xen_pcpu_init(void)
> >     return ret;
> >   }
> >   arch_initcall(xen_pcpu_init);
> > +
> > +#ifdef CONFIG_ACPI
> > +bool __init xen_processor_present(uint32_t acpi_id)
> > +{
> > +   struct pcpu *pcpu;
> > +   bool online = false;
> > +
> > +   mutex_lock(&xen_pcpu_lock);
> > +   list_for_each_entry(pcpu, &xen_pcpus, list)
> > +           if (pcpu->acpi_id == acpi_id) {
> > +                   online = pcpu->flags & XEN_PCPU_FLAGS_ONLINE;
> > +                   break;
> > +           }
> > +   mutex_unlock(&xen_pcpu_lock);
> > +
> > +   return online;
> > +}
> > +#endif
> > diff --git a/include/xen/xen.h b/include/xen/xen.h
> > index 7adf59837c25..4410e74f3eb5 100644
> > --- a/include/xen/xen.h
> > +++ b/include/xen/xen.h
> > @@ -71,4 +71,14 @@ static inline void xen_free_unpopulated_pages(unsigned 
> > int nr_pages,
> >   }
> >   #endif
> > +#if defined(CONFIG_XEN_DOM0) && defined(CONFIG_ACPI) && defined(CONFIG_X86)
> > +bool __init xen_processor_present(uint32_t acpi_id);
> > +#else
> > +static inline bool xen_processor_present(uint32_t acpi_id)
> > +{
> > +   BUG();
> 
> Is this really a good idea?
> 
> Arm64 supports ACPI, too, as well as XEN_DOM0. I think you either need to
> provide a stub for that case, too, or you need make this stub non-fatal
> for callers (I guess returning false is fine, as currently there are no
> hypercalls on Arm which would allow to control physical CPUs based on
> ACPI-Id).

Currently CONFIG_ARCH_MIGHT_HAVE_ACPI_PDC is only selected for x86 and
ia64, so I assumed if we ever needed this for Arm someone would have
to write a proper handler for it for Xen.

Thanks, Roger.



 


Rackspace

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