All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kim Phillips <kim.phillips@amd.com>
To: Dave Hansen <dave.hansen@intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-kernel@vger.kernel.org
Cc: Dave Hansen <dave.hansen@linux.intel.com>,
	Len Brown <lenb@kernel.org>,
	Mario Limonciello <Mario.Limonciello@amd.com>,
	Peter Zijlstra <peterz@infradead.org>,
	Borislav Petkov <bp@alien8.de>,
	K Prateek Nayak <kprateek.nayak@amd.com>,
	linux-acpi@vger.kernel.org, Linux PM <linux-pm@vger.kernel.org>,
	stable@vger.kernel.org
Subject: Re: [PATCH] ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
Date: Fri, 23 Sep 2022 13:36:52 -0500	[thread overview]
Message-ID: <edfe5f4c-70fa-5fcc-868f-497c428445f1@amd.com> (raw)
In-Reply-To: <54572271-d5ca-820f-911e-19fd9d80ae2c@intel.com>

On 9/22/22 2:01 PM, Dave Hansen wrote:
> On 9/22/22 11:53, Rafael J. Wysocki wrote:
>> Acked-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
>>
>> or do you want me to pick this up?
> 
> I'll just stick it in x86/urgent.
> 
> It's modifying code in a x86 #ifdef.  I'll call it a small enclave of
> sovereign x86 territory in ACPI land, just like an embassy. ;)

Can it be cc:stable@vger.kernel.org, since it applies cleanly as far
back as this v5.4 commit?:

commit fa583f71a99c85e52781ed877c82c8757437b680

Author: Yin Fengwei <fengwei.yin@intel.com>

Date:   Thu Oct 24 15:04:20 2019 +0800



     ACPI: processor_idle: Skip dummy wait if kernel is in guest


Thanks,

Kim

  reply	other threads:[~2022-09-23 18:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20220922184745.3252932-1-dave.hansen@intel.com>
2022-09-22 18:53 ` [PATCH] ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Rafael J. Wysocki
2022-09-22 18:57   ` Limonciello, Mario
2022-09-22 19:01   ` Dave Hansen
2022-09-23 18:36     ` Kim Phillips [this message]
2022-09-26 21:49       ` Dave Hansen
2022-09-23 20:35 ` K Prateek Nayak
2022-09-23 22:29 ` [tip: x86/urgent] " tip-bot2 for Dave Hansen

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=edfe5f4c-70fa-5fcc-868f-497c428445f1@amd.com \
    --to=kim.phillips@amd.com \
    --cc=Mario.Limonciello@amd.com \
    --cc=bp@alien8.de \
    --cc=dave.hansen@intel.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=kprateek.nayak@amd.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=peterz@infradead.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.