Linux ACPI
 help / color / mirror / Atom feed
From: Khalid Ali <khaliidcaliy@gmail.com>
To: peterz@infradead.org
Cc: bp@alien8.de, dave.hansen@linux.intel.com, hpa@zytor.com,
	khaliidcaliy@gmail.com, lenb@kernel.org,
	linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
	mingo@redhat.com, rafael@kernel.org, tglx@linutronix.de,
	x86@kernel.org
Subject: Re: [PATCH] x86/ACPI: invalidate all cache lines on ACPI C-state transitions
Date: Mon, 26 May 2025 17:04:52 +0000	[thread overview]
Message-ID: <20250526170616.1144-1-khaliidcaliy@gmail.com> (raw)
In-Reply-To: <20250526160753.GS39944@noisy.programming.kicks-ass.net>

> > > 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.

      reply	other threads:[~2025-05-26 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-25 18:00 [PATCH] x86/ACPI: invalidate all cache lines on ACPI C-state transitions Khalid Ali
2025-05-26 12:00 ` Peter Zijlstra
2025-05-26 13:45   ` Khalid Ali
2025-05-26 16:07     ` Peter Zijlstra
2025-05-26 17:04       ` Khalid Ali [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=20250526170616.1144-1-khaliidcaliy@gmail.com \
    --to=khaliidcaliy@gmail.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@linux.intel.com \
    --cc=hpa@zytor.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@redhat.com \
    --cc=peterz@infradead.org \
    --cc=rafael@kernel.org \
    --cc=tglx@linutronix.de \
    --cc=x86@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