From: "Huang, Sean Z" <sean.z.huang@intel.com>
To: Intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [RFC-v4 20/26] drm/i915/pxp: Add i915 trace logs for PXP operations
Date: Tue, 1 Dec 2020 20:03:35 -0800 [thread overview]
Message-ID: <20201202040341.31981-21-sean.z.huang@intel.com> (raw)
In-Reply-To: <20201202040341.31981-1-sean.z.huang@intel.com>
Add several i915 trace logs for PXP calls for debugging or
performance measurement, including:
(1) PXP ioctl
(2) PXP teardown callbacks
To trun on this feature, we need to set
"CONFIG_DRM_I915_LOW_LEVEL_TRACEPOINTS=y" in .config for compiling
the Linux kernel.
Signed-off-by: Huang, Sean Z <sean.z.huang@intel.com>
---
drivers/gpu/drm/i915/i915_trace.h | 44 ++++++++++++++++++++++++++++
drivers/gpu/drm/i915/pxp/intel_pxp.c | 6 ++++
2 files changed, 50 insertions(+)
diff --git a/drivers/gpu/drm/i915/i915_trace.h b/drivers/gpu/drm/i915/i915_trace.h
index a4addcc64978..36470e20dc61 100644
--- a/drivers/gpu/drm/i915/i915_trace.h
+++ b/drivers/gpu/drm/i915/i915_trace.h
@@ -1031,6 +1031,50 @@ DEFINE_EVENT(i915_context, i915_context_free,
TP_ARGS(ctx)
);
+TRACE_EVENT(i915_pxp_ops_ioctl,
+ TP_PROTO(struct drm_device *dev, void *data, struct drm_file *file, u32 action),
+ TP_ARGS(dev, data, file, action),
+
+ TP_STRUCT__entry(
+ __field(struct drm_device *, dev)
+ __field(void *, data)
+ __field(struct drm_file *, file)
+ __field(u32, action)
+ ),
+
+ TP_fast_assign(
+ __entry->dev = dev;
+ __entry->data = data;
+ __entry->file = file;
+ __entry->action = action;
+ ),
+
+ TP_printk("dev=%p, data=%p, file=%p, action=%u",
+ __entry->dev, __entry->data, __entry->file, __entry->action)
+);
+
+TRACE_EVENT(i915_pxp_teardown_required_callback,
+ TP_PROTO(bool global_state_attacked),
+ TP_ARGS(global_state_attacked),
+
+ TP_STRUCT__entry(__field(bool, global_state_attacked)),
+
+ TP_fast_assign(__entry->global_state_attacked = global_state_attacked;),
+
+ TP_printk("global_state_attacked=%s", yesno(__entry->global_state_attacked))
+);
+
+TRACE_EVENT(i915_pxp_global_terminate_complete_callback,
+ TP_PROTO(bool global_state_attacked),
+ TP_ARGS(global_state_attacked),
+
+ TP_STRUCT__entry(__field(bool, global_state_attacked)),
+
+ TP_fast_assign(__entry->global_state_attacked = global_state_attacked;),
+
+ TP_printk("global_state_attacked=%s", yesno(__entry->global_state_attacked))
+);
+
#endif /* _I915_TRACE_H_ */
/* This part must be outside protection */
diff --git a/drivers/gpu/drm/i915/pxp/intel_pxp.c b/drivers/gpu/drm/i915/pxp/intel_pxp.c
index 766797b7854e..8134b39c7419 100644
--- a/drivers/gpu/drm/i915/pxp/intel_pxp.c
+++ b/drivers/gpu/drm/i915/pxp/intel_pxp.c
@@ -8,6 +8,7 @@
#include "intel_pxp_context.h"
#include "intel_pxp_sm.h"
#include "intel_pxp_tee.h"
+#include "i915_trace.h"
int i915_pxp_ops_ioctl(struct drm_device *dev, void *data, struct drm_file *drmfile)
{
@@ -23,6 +24,8 @@ int i915_pxp_ops_ioctl(struct drm_device *dev, void *data, struct drm_file *drmf
if (copy_from_user(&pxp_info, pxp_ops->info_ptr, sizeof(pxp_info)) != 0)
return -EFAULT;
+ trace_i915_pxp_ops_ioctl(dev, data, drmfile, pxp_info.action);
+
mutex_lock(&i915->pxp.ctx->ctx_mutex);
if (i915->pxp.ctx->global_state_in_suspend) {
@@ -198,6 +201,8 @@ static int intel_pxp_teardown_required_callback(struct drm_i915_private *i915)
mutex_unlock(&i915->pxp.ctx->ctx_mutex);
+ trace_i915_pxp_teardown_required_callback(i915->pxp.ctx->global_state_attacked);
+
return ret;
}
@@ -220,6 +225,7 @@ static int intel_pxp_global_terminate_complete_callback(struct drm_i915_private
end:
mutex_unlock(&i915->pxp.ctx->ctx_mutex);
+ trace_i915_pxp_global_terminate_complete_callback(i915->pxp.ctx->global_state_attacked);
return ret;
}
--
2.17.1
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-12-02 4:04 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-02 4:03 [Intel-gfx] [RFC-v4 00/26] Introduce Intel PXP component Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 01/26] drm/i915/pxp: " Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 02/26] drm/i915/pxp: Enable PXP irq worker and callback stub Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 03/26] drm/i915/pxp: Add PXP context for logical hardware states Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 04/26] drm/i915/pxp: set KCR reg init during the boot time Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 05/26] drm/i915/pxp: Implement ioctl action to set the user space context Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 06/26] drm/i915/pxp: Add PXP-related registers into allowlist Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 07/26] drm/i915/pxp: Read register to check hardware session state Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 08/26] drm/i915/pxp: Implement funcs to get/set PXP tag Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 09/26] drm/i915/pxp: Implement ioctl action to reserve session slot Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 10/26] drm/i915/pxp: Implement ioctl action to set session in play Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 11/26] drm/i915/pxp: Func to send hardware session termination Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 12/26] drm/i915/pxp: Implement ioctl action to terminate the session Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 13/26] drm/i915/pxp: Enable ioctl action to query PXP tag Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 14/26] drm/i915/pxp: Destroy all type0 sessions upon teardown Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 15/26] drm/i915/pxp: Termiante the session upon app crash Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 16/26] drm/i915/pxp: Enable PXP power management Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 17/26] drm/i915/pxp: Implement funcs to create the TEE channel Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 18/26] drm/i915/pxp: Implement ioctl action to send TEE commands Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 19/26] drm/i915/pxp: Create the arbitrary session after boot Huang, Sean Z
2020-12-02 4:03 ` Huang, Sean Z [this message]
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 21/26] drm/i915/pxp: Expose session state for display protection flip Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 22/26] mei: pxp: export pavp client to me client bus Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 23/26] drm/i915/uapi: introduce drm_i915_gem_create_ext Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 24/26] drm/i915/pxp: User interface for Protected buffer Huang, Sean Z
2020-12-04 14:24 ` Lionel Landwerlin
2020-12-04 18:56 ` Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 25/26] drm/i915/pxp: Add plane decryption support Huang, Sean Z
2020-12-02 4:03 ` [Intel-gfx] [RFC-v4 26/26] drm/i915/pxp: Enable the PXP ioctl for protected session Huang, Sean Z
2020-12-02 4:18 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for Introduce Intel PXP component (rev4) Patchwork
2020-12-02 4:48 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-12-02 7:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20201202040341.31981-21-sean.z.huang@intel.com \
--to=sean.z.huang@intel.com \
--cc=Intel-gfx@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;
as well as URLs for NNTP newsgroup(s).