From: Thomas Gleixner <tglx@linutronix.de>
To: Roman Kisel <romank@linux.microsoft.com>,
ardb@kernel.org, bp@alien8.de, dave.hansen@linux.intel.com,
decui@microsoft.com, dimitri.sivanich@hpe.com,
haiyangz@microsoft.com, hpa@zytor.com, imran.f.khan@oracle.com,
jacob.jun.pan@linux.intel.com, jgross@suse.com,
justin.ernst@hpe.com, kprateek.nayak@amd.com, kyle.meyer@hpe.com,
kys@microsoft.com, lenb@kernel.org, mingo@redhat.com,
nikunj@amd.com, papaluri@amd.com, perry.yuan@amd.com,
peterz@infradead.org, rafael@kernel.org,
romank@linux.microsoft.com, russ.anderson@hpe.com,
steve.wahl@hpe.com, thomas.lendacky@amd.com,
tim.c.chen@linux.intel.com, tony.luck@intel.com,
wei.liu@kernel.org, xin@zytor.com, yuehaibing@huawei.com,
linux-acpi@vger.kernel.org, linux-hyperv@vger.kernel.org,
linux-kernel@vger.kernel.org, x86@kernel.org
Cc: apais@microsoft.com, benhill@microsoft.com,
bperkins@microsoft.com, sunilmut@microsoft.com
Subject: Re: [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the wakeup AP callback
Date: Fri, 02 May 2025 18:14:41 +0200 [thread overview]
Message-ID: <8734dnouq6.ffs@tglx> (raw)
In-Reply-To: <20250430204720.108962-1-romank@linux.microsoft.com>
On Wed, Apr 30 2025 at 13:47, Roman Kisel wrote:
> When starting APs, confidential guests and paravisor guests
> need to know the CPU number, and the pattern of using the linear
> search has emerged in several places. With N processors that leads
> to the O(N^2) time complexity.
>
> Provide the CPU number in the AP wake up callback so that one can
> get the CPU number in constant time.
>
> Suggested-by: Michael Kelley <mhklinux@outlook.com>
> Signed-off-by: Roman Kisel <romank@linux.microsoft.com>
> Reviewed-by: Tom Lendacky <thomas.lendacky@amd.com>
Reviewed-by: Thomas Gleixner <tglx@linutronix.de>
next prev parent reply other threads:[~2025-05-02 16:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-30 20:47 [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the wakeup AP callback Roman Kisel
2025-04-30 22:39 ` Michael Kelley
2025-05-02 16:14 ` Thomas Gleixner [this message]
2025-05-02 17:32 ` Wei Liu
2025-05-05 17:22 ` Roman Kisel
2025-05-05 18:01 ` Wei Liu
2025-05-05 18:12 ` Dave Hansen
2025-05-06 2:52 ` Wei Liu
2025-05-06 2:57 ` Wei Liu
2025-05-06 2:58 ` Wei Liu
2025-05-07 6:22 ` [EXTERNAL] " Saurabh Singh Sengar
2025-05-07 6:23 ` Wei Liu
2025-05-07 17:07 ` Roman Kisel
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=8734dnouq6.ffs@tglx \
--to=tglx@linutronix.de \
--cc=apais@microsoft.com \
--cc=ardb@kernel.org \
--cc=benhill@microsoft.com \
--cc=bp@alien8.de \
--cc=bperkins@microsoft.com \
--cc=dave.hansen@linux.intel.com \
--cc=decui@microsoft.com \
--cc=dimitri.sivanich@hpe.com \
--cc=haiyangz@microsoft.com \
--cc=hpa@zytor.com \
--cc=imran.f.khan@oracle.com \
--cc=jacob.jun.pan@linux.intel.com \
--cc=jgross@suse.com \
--cc=justin.ernst@hpe.com \
--cc=kprateek.nayak@amd.com \
--cc=kyle.meyer@hpe.com \
--cc=kys@microsoft.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hyperv@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nikunj@amd.com \
--cc=papaluri@amd.com \
--cc=perry.yuan@amd.com \
--cc=peterz@infradead.org \
--cc=rafael@kernel.org \
--cc=romank@linux.microsoft.com \
--cc=russ.anderson@hpe.com \
--cc=steve.wahl@hpe.com \
--cc=sunilmut@microsoft.com \
--cc=thomas.lendacky@amd.com \
--cc=tim.c.chen@linux.intel.com \
--cc=tony.luck@intel.com \
--cc=wei.liu@kernel.org \
--cc=x86@kernel.org \
--cc=xin@zytor.com \
--cc=yuehaibing@huawei.com \
/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