linux-kernel - Re: [PATCH] x86/ACPI: invalidate all cache lines on ACPI C-state transitions

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] [day] [month] [year] [list]

Message-ID: <20250526170616.1144-1-khaliidcaliy@gmail.com>
Date: Mon, 26 May 2025 17:04:52 +0000
From: Khalid Ali <khaliidcaliy@...il.com>
To: peterz@...radead.org
Cc: bp@...en8.de,
	dave.hansen@...ux.intel.com,
	hpa@...or.com,
	khaliidcaliy@...il.com,
	lenb@...nel.org,
	linux-acpi@...r.kernel.org,
	linux-kernel@...r.kernel.org,
	mingo@...hat.com,
	rafael@...nel.org,
	tglx@...utronix.de,
	x86@...nel.org
Subject: Re: [PATCH] x86/ACPI: invalidate all cache lines on ACPI C-state transitions

> > > This is absolutely insane. This day and age, nobody should use WBINVD
> > > ever. We've managed to not do this for decades, and I'm thinking that
> > > either the SPEC is 'mistaken' or otherwise out of line with reality.
> 
> > > If you hate performance, and you want to break things like CAT, feel
> > > free to put this in your own kernel.
> > Sorry, i made a mistake, i meant ACPI 6.4 and 6.5. I already resent this patch
> > please check the resended one.
> Doesn't matter. We're categorically not going to be doing this. Rafael,
> who do we kick to get the ACPI SPEC fixed?

First of all, am i talking to some kinda roasting robot?
Please talk professionally, fix the way you talk before you fix a code (of course if i am talking to human being).
I am here waiting for a real answer, so please just tell me i don't know how hard is to say yes or no. 
And tell me the reason.

BTW, if your english isn't perfect, i get that and i am sorry for what i said.