From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>,
Rodrigo Vivi <rodrigo.vivi@intel.com>,
Lucas De Marchi <lucas.demarchi@intel.com>,
Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Subject: [PATCH v2 0/2] New force-wake guard class
Date: Mon, 18 Nov 2024 19:45:09 +0100 [thread overview]
Message-ID: <20241118184511.258-1-michal.wajdeczko@intel.com> (raw)
There is support for 'classes' with constructor and destructor
semantics that can be used for any scope-based resource management,
like device force-wake management.
This should allow us to use:
CLASS(xe_fw, var)(fw, XE_FORCEWAKE_ALL);
or
guard(xe_fw)(fw, XE_FW_GT);
or
scoped_guard(xe_fw, fw, XE_FW_GT)
foo();
without any concern of leaking the force-wake references.
v1: https://patchwork.freedesktop.org/series/134958/
v2: rebased
Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Cc: Himal Prasad Ghimiray <himal.prasad.ghimiray@intel.com>
Michal Wajdeczko (2):
drm/xe: Introduce force-wake guard class
drm/xe: Use new force-wake guard class in xe_mocs.c
drivers/gpu/drm/xe/xe_force_wake.h | 12 ++++++++++++
drivers/gpu/drm/xe/xe_force_wake_types.h | 10 ++++++++++
drivers/gpu/drm/xe/xe_mocs.c | 10 +++-------
3 files changed, 25 insertions(+), 7 deletions(-)
--
2.43.0
next reply other threads:[~2024-11-18 18:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 18:45 Michal Wajdeczko [this message]
2024-11-18 18:45 ` [PATCH v2 1/2] drm/xe: Introduce force-wake guard class Michal Wajdeczko
2024-11-19 18:47 ` Rodrigo Vivi
2024-11-19 19:21 ` Raag Jadav
2024-11-19 19:59 ` Lucas De Marchi
2024-11-19 20:26 ` Michal Wajdeczko
2024-11-25 12:11 ` Rodrigo Vivi
2024-11-25 13:53 ` Raag Jadav
2024-11-18 18:45 ` [PATCH v2 2/2] drm/xe: Use new force-wake guard class in xe_mocs.c Michal Wajdeczko
2024-11-19 20:03 ` Lucas De Marchi
2024-11-19 21:05 ` Michal Wajdeczko
2024-11-21 4:55 ` Matthew Brost
2024-11-21 20:53 ` Lucas De Marchi
2024-11-18 18:54 ` ✓ CI.Patch_applied: success for New force-wake guard class Patchwork
2024-11-18 18:55 ` ✓ CI.checkpatch: " Patchwork
2024-11-18 18:57 ` ✓ CI.KUnit: " Patchwork
2024-11-18 19:20 ` ✓ CI.Build: " Patchwork
2024-11-18 19:23 ` ✓ CI.Hooks: " Patchwork
2024-11-18 19:24 ` ✓ CI.checksparse: " Patchwork
2024-11-19 1:57 ` ✗ CI.FULL: failure " Patchwork
2024-11-19 7:29 ` ✓ CI.BAT: success " Patchwork
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=20241118184511.258-1-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=himal.prasad.ghimiray@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lucas.demarchi@intel.com \
--cc=rodrigo.vivi@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