From: Mario Limonciello <superm1@kernel.org>
To: "Shyam Sundar S K" <Shyam-sundar.S-k@amd.com>,
"Ilpo Järvinen" <ilpo.jarvinen@linux.intel.com>
Cc: Hans de Goede <hdegoede@redhat.com>,
platform-driver-x86@vger.kernel.org (open list:AMD PMF DRIVER),
Mario Limonciello <mario.limonciello@amd.com>
Subject: [PATCH v3 0/3] Improved cleanup handling for amd-pmf
Date: Mon, 12 May 2025 16:11:51 -0500 [thread overview]
Message-ID: <20250512211154.2510397-1-superm1@kernel.org> (raw)
From: Mario Limonciello <mario.limonciello@amd.com>
I noticed some memory problems with unloading and reloading amd-pmf.
These were root caused with a double free.
This series cleans up that double free by switching to device managed
allocations and also fixes other problems observed in earlier iterations
of the patches.
v2->v3:
* Add Dan's suggestion
* Use device managed allocations
* Simplify error flow
v2: https://lore.kernel.org/platform-driver-x86/20250507020838.2962896-1-superm1@kernel.org/
Mario Limonciello (3):
platform/x86/amd: pmf: Use device managed allocations
platform/x86/amd: pmf: Prevent amd_pmf_tee_deinit() from running twice
platform/x86/amd: pmf: Simplify error flow in amd_pmf_init_smart_pc()
drivers/platform/x86/amd/pmf/core.c | 3 +-
drivers/platform/x86/amd/pmf/tee-if.c | 100 +++++++++-----------------
2 files changed, 33 insertions(+), 70 deletions(-)
base-commit: bfcfe6d335a967f8ea0c1980960e6f0205b5de6e
--
2.43.0
next reply other threads:[~2025-05-12 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 21:11 Mario Limonciello [this message]
2025-05-12 21:11 ` [PATCH v3 1/3] platform/x86/amd: pmf: Use device managed allocations Mario Limonciello
2025-05-14 10:21 ` Ilpo Järvinen
2025-05-14 15:05 ` Mario Limonciello
2025-05-15 11:58 ` Ilpo Järvinen
2025-05-12 21:11 ` [PATCH v3 2/3] platform/x86/amd: pmf: Prevent amd_pmf_tee_deinit() from running twice Mario Limonciello
2025-05-12 21:11 ` [PATCH v3 3/3] platform/x86/amd: pmf: Simplify error flow in amd_pmf_init_smart_pc() Mario Limonciello
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=20250512211154.2510397-1-superm1@kernel.org \
--to=superm1@kernel.org \
--cc=Shyam-sundar.S-k@amd.com \
--cc=hdegoede@redhat.com \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=mario.limonciello@amd.com \
--cc=platform-driver-x86@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox