mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Penny Zheng <Penny.Zheng@amd.com>
To: Juergen Gross <jgross@suse.com>,
	Stefano Stabellini <sstabellini@kernel.org>,
	Oleksandr Tyshchenko <oleksandr_tyshchenko@epam.com>
Cc: Ray Huang <Ray.Huang@amd.com>,
	Xenia Ragiadakou <Xenia.Ragiadakou@amd.com>,
	Jason Andryuk <jason.andryuk@amd.com>,
	"Penny Zheng" <Penny.Zheng@amd.com>,
	<xen-devel@lists.xenproject.org>, <linux-kernel@vger.kernel.org>
Subject: [PATCH v1 0/4] xen/acpi: introduce cppc performance hypercall
Date: Wed, 4 Dec 2024 16:24:26 +0800	[thread overview]
Message-ID: <20241204082430.469092-1-Penny.Zheng@amd.com> (raw)

When running as Xen dom0 PVH guest, MADT table is customized
and may have the "wrong" UID processor number, which is
inconsistent with the UID in Processor entry in native DSDT.

As a result, during ACPI boot-up for dom0, linux fails to set
up proper processor logical id <-> physical id map(acpi_map_cpuid).
Furthermore, It leads to that some ACPI processor feature capibility,
like per-cpu cpc_desc structure, failed to be correctly stored
and processed.

With upstreaming "amd-pstate CPU Performance Scaling Driver"(
https://lore.kernel.org/all/20241203081111.463400-1-Penny.Zheng@amd.com/)
to Xen community, amd-pstate driver is supported on Xen platform.
And as Xen is uncapable of parsing the ACPI dynamic table, like _CPC
entry, this patch serie introduces a new sub-hypercall XEN_PM_CPPC
to deliver CPPC performance capability data.

This patch serie is based on commit "xen/acpi: upload power and performance
related data from a PVH dom0"(
https://patchwork.kernel.org/project/xen-devel/patch/20241203225338.1336-1-jason.andryuk@amd.com/),
which is still under review.

Penny Zheng (3):
  acpi/cppc: extract _cpc entry parsing logic
  xen/cppc: get xen-required cppc perf caps data
  xen/cppc: introduce cppc data upload sub-hypercall

Roger Pau Monné (1):
  xen/acpi: upload power and performance related data from a PVH dom0

 drivers/acpi/cppc_acpi.c         | 206 +++++++++++++++-----
 drivers/xen/pcpu.c               |   3 +-
 drivers/xen/xen-acpi-processor.c | 320 +++++++++++++++++++++++++++++--
 include/acpi/cppc_acpi.h         |   5 +
 include/acpi/processor.h         |   2 +
 include/xen/interface/platform.h |  11 ++
 include/xen/xen.h                |   2 +-
 7 files changed, 477 insertions(+), 72 deletions(-)

-- 
2.34.1


             reply	other threads:[~2024-12-04  8:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-04  8:24 Penny Zheng [this message]
2024-12-04  8:24 ` [PATCH v1 1/4] xen/acpi: upload power and performance related data from a PVH dom0 Penny Zheng
2024-12-04  8:29   ` Jürgen Groß
2024-12-04 19:11     ` Jason Andryuk
2024-12-05  5:24       ` Penny, Zheng
2024-12-04  8:24 ` [PATCH v1 2/4] acpi/cppc: extract _cpc entry parsing logic Penny Zheng
2024-12-04  8:24 ` [PATCH v1 3/4] xen/cppc: get xen-required cppc perf caps data Penny Zheng
2024-12-04  8:24 ` [PATCH v1 4/4] xen/cppc: introduce cppc data upload sub-hypercall Penny Zheng

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20241204082430.469092-1-Penny.Zheng@amd.com \
    --to=penny.zheng@amd.com \
    --cc=Ray.Huang@amd.com \
    --cc=Xenia.Ragiadakou@amd.com \
    --cc=jason.andryuk@amd.com \
    --cc=jgross@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleksandr_tyshchenko@epam.com \
    --cc=sstabellini@kernel.org \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®