lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID:
 <KUZP153MB1444BF0D51C59D3E24A61B13BE88A@KUZP153MB1444.APCP153.PROD.OUTLOOK.COM>
Date: Wed, 7 May 2025 06:22:24 +0000
From: Saurabh Singh Sengar <ssengar@...rosoft.com>
To: Wei Liu <wei.liu@...nel.org>, Roman Kisel <romank@...ux.microsoft.com>
CC: "ardb@...nel.org" <ardb@...nel.org>, "bp@...en8.de" <bp@...en8.de>,
	"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>, Dexuan Cui
	<decui@...rosoft.com>, "dimitri.sivanich@....com" <dimitri.sivanich@....com>,
	Haiyang Zhang <haiyangz@...rosoft.com>, "hpa@...or.com" <hpa@...or.com>,
	"imran.f.khan@...cle.com" <imran.f.khan@...cle.com>,
	"jacob.jun.pan@...ux.intel.com" <jacob.jun.pan@...ux.intel.com>,
	"jgross@...e.com" <jgross@...e.com>, "justin.ernst@....com"
	<justin.ernst@....com>, "kprateek.nayak@....com" <kprateek.nayak@....com>,
	"kyle.meyer@....com" <kyle.meyer@....com>, KY Srinivasan <kys@...rosoft.com>,
	"lenb@...nel.org" <lenb@...nel.org>, "mingo@...hat.com" <mingo@...hat.com>,
	"nikunj@....com" <nikunj@....com>, "papaluri@....com" <papaluri@....com>,
	"perry.yuan@....com" <perry.yuan@....com>, "peterz@...radead.org"
	<peterz@...radead.org>, "rafael@...nel.org" <rafael@...nel.org>,
	"russ.anderson@....com" <russ.anderson@....com>, "steve.wahl@....com"
	<steve.wahl@....com>, "tglx@...utronix.de" <tglx@...utronix.de>,
	"thomas.lendacky@....com" <thomas.lendacky@....com>,
	"tim.c.chen@...ux.intel.com" <tim.c.chen@...ux.intel.com>,
	"tony.luck@...el.com" <tony.luck@...el.com>, "xin@...or.com" <xin@...or.com>,
	"yuehaibing@...wei.com" <yuehaibing@...wei.com>, "linux-acpi@...r.kernel.org"
	<linux-acpi@...r.kernel.org>, "linux-hyperv@...r.kernel.org"
	<linux-hyperv@...r.kernel.org>, "linux-kernel@...r.kernel.org"
	<linux-kernel@...r.kernel.org>, "x86@...nel.org" <x86@...nel.org>, Allen Pais
	<apais@...rosoft.com>, Ben Hillis <Ben.Hillis@...rosoft.com>, Brian Perkins
	<Brian.Perkins@...rosoft.com>, Sunil Muthuswamy <sunilmut@...rosoft.com>
Subject: RE: [EXTERNAL] Re: [PATCH hyperv-next v3] arch/x86: Provide the CPU
 number in the wakeup AP callback

> On Wed, Apr 30, 2025 at 01:47:20PM -0700, 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@...look.com>
> > Signed-off-by: Roman Kisel <romank@...ux.microsoft.com>
> > Reviewed-by: Tom Lendacky <thomas.lendacky@....com>
> 
> Queued to hyperv-next. Thanks.

We need to update numachip_wakeup_secondary as well, otherwise this will break the builds.

Regards,
Saurabh


Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ