mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Ricardo Neri <ricardo.neri-calderon@linux.intel.com>
To: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: Chen Yu <yu.c.chen@intel.com>, Len Brown <len.brown@intel.com>,
	Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
	Stanislaw Gruszka <stanislaw.gruszka@linux.intel.com>,
	Zhang Rui <rui.zhang@intel.com>, Zhao Liu <zhao1.liu@intel.com>,
	linux-pm@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/4] thermal: intel: hfi: Fix memory corruption on resume from hibernation
Date: Tue,  2 Jan 2024 20:14:55 -0800	[thread overview]
Message-ID: <20240103041459.11113-1-ricardo.neri-calderon@linux.intel.com> (raw)

Hi,

This is v2 of this series. You can read the overview and motivation in the
cover letter of v1 [1].

I smoke-retested this version on a Meteor Lake system. It completed 50
cycles of suspend-to-disk and resume. I completed longer testing for v1.

Changes since v1:
 * Added locking to hfi_pm_notify() to serialize RMW operations on the
   MSR_IA32_HW_FEEDBACK_CONFIG register. (Rafael)
 * Relocated a comment regarding the reallocation of HFI memory to
   patch 3/4. (Rafael)
 * Clarified that patch 1/4 does not introduce functional changes.
   (Rafael)
 * Indicated the first stable version on which this patchset should be
   backported.
 * Renamed hfi_do_pm_[enable|disable]() as hfi_do_[enable|disable]() for
   future reuse. (Stan)
 * Registered the HFI suspend notifier towards the end of
   intel_hfi_init(). (Stan)

Thanks and BR,
Ricardo

[1]. https://lore.kernel.org/all/20231227062940.10780-1-ricardo.neri-calderon@linux.intel.com/

Ricardo Neri (4):
  thermal: intel: hfi: Refactor enabling code into helper functions
  thermal: intel: hfi: Enable an HFI instance from its first online CPU
  thermal: intel: hfi: Disable an HFI instance when all its CPUs go
    offline
  thermal: intel: hfi: Add a suspend notifier

 drivers/thermal/intel/intel_hfi.c | 153 +++++++++++++++++++++++++-----
 1 file changed, 127 insertions(+), 26 deletions(-)

-- 
2.25.1


             reply	other threads:[~2024-01-03  4:13 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-03  4:14 Ricardo Neri [this message]
2024-01-03  4:14 ` [PATCH v2 1/4] thermal: intel: hfi: Refactor enabling code into helper functions Ricardo Neri
2024-01-03  4:14 ` [PATCH v2 2/4] thermal: intel: hfi: Enable an HFI instance from its first online CPU Ricardo Neri
2024-01-03  4:14 ` [PATCH v2 3/4] thermal: intel: hfi: Disable an HFI instance when all its CPUs go offline Ricardo Neri
2024-01-03  4:14 ` [PATCH v2 4/4] thermal: intel: hfi: Add a suspend notifier Ricardo Neri
2024-01-03 13:34   ` Rafael J. Wysocki
2024-01-03 13:38     ` Rafael J. Wysocki
2024-01-04  3:02       ` Ricardo Neri
2024-01-03 15:02     ` Stanislaw Gruszka
2024-01-03 18:21       ` Rafael J. Wysocki
2024-01-04  3:04     ` Ricardo Neri
2024-01-03 13:15 ` [PATCH v2 0/4] thermal: intel: hfi: Fix memory corruption on resume from hibernation Rafael J. Wysocki

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=20240103041459.11113-1-ricardo.neri-calderon@linux.intel.com \
    --to=ricardo.neri-calderon@linux.intel.com \
    --cc=len.brown@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rui.zhang@intel.com \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=stanislaw.gruszka@linux.intel.com \
    --cc=yu.c.chen@intel.com \
    --cc=zhao1.liu@intel.com \
    /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

all inboxes | Powered by JetHome®