Linux driver-core infrastructure
 help / color / mirror / Atom feed
From: Feng Tang <feng.tang@linux.alibaba.com>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sudeep Holla <sudeep.holla@kernel.org>,
	rafael@kernel.org, Danilo Krummrich <dakr@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	David Hildenbrand <david@kernel.org>,
	linux-kernel@vger.kernel.org, driver-core@lists.linux.dev
Subject: Re: [PATCH RFC] arch_topology: Introduce nr_possible_packages
Date: Wed, 13 May 2026 17:46:33 +0800	[thread overview]
Message-ID: <agRIebOKjDEe8Kmi@U-2FWC9VHC-2323.local> (raw)
In-Reply-To: <agPVYkyVMcUye3cn@U-2FWC9VHC-2323.local>

On Wed, May 13, 2026 at 09:35:30AM +0800, Feng Tang wrote:
[...] 
> > And you don't have a user for this, so we can't verify how it actually
> > works :(
> 
> Good point. Internally we have some PMU driver using this, but the HW is
> not public and the drive hasn't been posted yet.
> 
> As for validation, we tested on production 1P platform, internal 2P
> platform, and QEMU's multi-socket case.
> 
> I checked a production arm64 2P platform 'Kunpeng 920', and from the
> output of "cat /sys/devices/system/cpu/cpu*/topology/physical_package_id",
> the patch should work fine. I don't have root right of it yet, will try
> to really run the patch on it.

Just tried 7.1-rc3 + this patch on the 2P arm64 'Kunpeng 920' server, and
it showed the correct package number:

"[    0.011284] ACPI: System has 2 Package(s) detected"

Thanks,
Feng

      reply	other threads:[~2026-05-13  9:46 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-12 15:05 [PATCH RFC] arch_topology: Introduce nr_possible_packages Feng Tang
2026-05-12 15:51 ` Greg Kroah-Hartman
2026-05-13  1:35   ` Feng Tang
2026-05-13  9:46     ` Feng Tang [this message]

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=agRIebOKjDEe8Kmi@U-2FWC9VHC-2323.local \
    --to=feng.tang@linux.alibaba.com \
    --cc=catalin.marinas@arm.com \
    --cc=dakr@kernel.org \
    --cc=david@kernel.org \
    --cc=driver-core@lists.linux.dev \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=sudeep.holla@kernel.org \
    --cc=will@kernel.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