From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] [PATCH 1/5] drm/xe: Define DRM_XE_DEBUG_SRIOV config
Date: Tue, 28 Nov 2023 16:15:03 +0100 [thread overview]
Message-ID: <20231128151507.1015-2-michal.wajdeczko@intel.com> (raw)
In-Reply-To: <20231128151507.1015-1-michal.wajdeczko@intel.com>
We will be using extra logs during enabling of the SR-IOV features
or when adding support for new platforms. Define separate config
flag to keep that low level logs disabled if we're not debugging.
Signed-off-by: Michal Wajdeczko <michal.wajdeczko@intel.com>
---
drivers/gpu/drm/xe/Kconfig.debug | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/xe/Kconfig.debug b/drivers/gpu/drm/xe/Kconfig.debug
index 11bb13c73e7b..549065f57a78 100644
--- a/drivers/gpu/drm/xe/Kconfig.debug
+++ b/drivers/gpu/drm/xe/Kconfig.debug
@@ -40,6 +40,16 @@ config DRM_XE_DEBUG_VM
If in doubt, say "N".
+config DRM_XE_DEBUG_SRIOV
+ bool "Enable extra SR-IOV debugging"
+ default n
+ help
+ Enable extra SR-IOV debugging info.
+
+ Recommended for driver developers only.
+
+ If in doubt, say "N".
+
config DRM_XE_DEBUG_MEM
bool "Enable passing SYS/VRAM addresses to user space"
default n
--
2.25.1
next prev parent reply other threads:[~2023-11-28 15:15 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 15:15 [Intel-xe] [PATCH 0/5] Introduce Local Memory Translation Table Michal Wajdeczko
2023-11-28 15:15 ` Michal Wajdeczko [this message]
2023-12-07 14:17 ` [Intel-xe] [PATCH 1/5] drm/xe: Define DRM_XE_DEBUG_SRIOV config Lucas De Marchi
2023-11-28 15:15 ` [Intel-xe] [PATCH 2/5] drm/xe: Introduce SR-IOV logging macros Michal Wajdeczko
2023-12-07 14:17 ` Lucas De Marchi
2023-11-28 15:15 ` [Intel-xe] [PATCH 3/5] drm/xe/pf: Introduce Local Memory Translation Table Michal Wajdeczko
2023-12-07 0:43 ` Michał Winiarski
2023-12-07 14:55 ` Michal Wajdeczko
2023-11-28 15:15 ` [Intel-xe] [PATCH 4/5] drm/xe/kunit: Enable CONFIG_PCI_IOV in .kunitconfig Michal Wajdeczko
2023-12-07 0:24 ` Michał Winiarski
2023-11-28 15:15 ` [Intel-xe] [PATCH 5/5] drm/xe/kunit: Add test for LMTT operations Michal Wajdeczko
2023-12-07 0:23 ` Michał Winiarski
2023-11-28 16:30 ` [Intel-xe] ✓ CI.Patch_applied: success for Introduce Local Memory Translation Table Patchwork
2023-11-28 16:30 ` [Intel-xe] ✗ CI.checkpatch: warning " Patchwork
2023-11-28 16:31 ` [Intel-xe] ✓ CI.KUnit: success " Patchwork
2023-11-28 16:39 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-11-28 16:39 ` [Intel-xe] ✗ CI.Hooks: failure " Patchwork
2023-11-28 16:41 ` [Intel-xe] ✓ CI.checksparse: success " Patchwork
2023-11-28 17:14 ` [Intel-xe] ✓ CI.BAT: " Patchwork
2023-12-11 21:21 ` [Intel-xe] [PATCH 0/5] " Rodrigo Vivi
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=20231128151507.1015-2-michal.wajdeczko@intel.com \
--to=michal.wajdeczko@intel.com \
--cc=intel-xe@lists.freedesktop.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