linux-kernel - Re: [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the wakeup AP callback

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: <aBl5hhE2mY5ygq8l@liuwe-devbox-ubuntu-v2.tail21d00.ts.net>
Date: Tue, 6 May 2025 02:52:54 +0000
From: Wei Liu <wei.liu@...nel.org>
To: Dave Hansen <dave.hansen@...el.com>
Cc: Wei Liu <wei.liu@...nel.org>, Roman Kisel <romank@...ux.microsoft.com>,
	ardb@...nel.org, bp@...en8.de, dave.hansen@...ux.intel.com,
	decui@...rosoft.com, dimitri.sivanich@....com,
	haiyangz@...rosoft.com, hpa@...or.com, imran.f.khan@...cle.com,
	jacob.jun.pan@...ux.intel.com, jgross@...e.com,
	justin.ernst@....com, kprateek.nayak@....com, kyle.meyer@....com,
	kys@...rosoft.com, lenb@...nel.org, mingo@...hat.com,
	nikunj@....com, papaluri@....com, perry.yuan@....com,
	peterz@...radead.org, rafael@...nel.org, russ.anderson@....com,
	steve.wahl@....com, tglx@...utronix.de, thomas.lendacky@....com,
	tim.c.chen@...ux.intel.com, tony.luck@...el.com, xin@...or.com,
	yuehaibing@...wei.com, linux-acpi@...r.kernel.org,
	linux-hyperv@...r.kernel.org, linux-kernel@...r.kernel.org,
	x86@...nel.org, apais@...rosoft.com, benhill@...rosoft.com,
	bperkins@...rosoft.com, sunilmut@...rosoft.com
Subject: Re: [PATCH hyperv-next v3] arch/x86: Provide the CPU number in the
 wakeup AP callback

On Mon, May 05, 2025 at 11:12:10AM -0700, Dave Hansen wrote:
> On 5/5/25 11:01, Wei Liu wrote:
> > You don't need to do that for this patch. Please point me to Thomas'
> > reply to the previous version and I can add the missing tag to patch
> > while I queue it.
> 
> It's right here:
> 
> 	https://lore.kernel.org/all/8734dnouq6.ffs@tglx/

Thanks for the pointer. This is appreciated.

> 
> It's pretty darn trivial to find if you do any of the following:
> 
> 1. Read this thread in your mail reader that understands threads, or
> 2. Look at this thread on lore, or
> 3. Run "b4 am" on the thread
> 
> Sure, it can be kinda hard to do #1/#2 on gigantic threads if there are
> a ton of replies from the maintainer. But there were 5 messages in this
> thread and only one from Thomas.
> 
> I'd highly suggest adding one or more of those tools to your maintainer
> toolbox! b4, especially, does all the work for you.

I use b4, too.

I wished I had more time to go over every things in my inbox. That's why
I asked Roman (and other contributors) to include whatever tags were
given during the review process while they submit new versions of their
patches.

Thanks,
Wei.