From: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
To: Ashutosh Dixit <ashutosh.dixit@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t 1/2] drm-uapi/xe: Sync with OA syncs uapi update
Date: Fri, 25 Oct 2024 12:36:13 -0700 [thread overview]
Message-ID: <ZxvzLU/InQ1Lcjgz@orsosgc001> (raw)
In-Reply-To: <20241025185205.1327235-2-ashutosh.dixit@intel.com>
On Fri, Oct 25, 2024 at 11:52:04AM -0700, Ashutosh Dixit wrote:
>Align with kernel commit c8507a25cebd ("drm/xe/oa/uapi: Define and parse OA
>sync properties") which adds OA syncs uapi.
>
>Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
Reviewed-by: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>
>---
> include/drm-uapi/xe_drm.h | 29 ++++++++++++++++++++++++-----
> 1 file changed, 24 insertions(+), 5 deletions(-)
>
>diff --git a/include/drm-uapi/xe_drm.h b/include/drm-uapi/xe_drm.h
>index f0a450db95..4a8a4a63e9 100644
>--- a/include/drm-uapi/xe_drm.h
>+++ b/include/drm-uapi/xe_drm.h
>@@ -3,8 +3,8 @@
> * Copyright © 2023 Intel Corporation
> */
>
>-#ifndef _XE_DRM_H_
>-#define _XE_DRM_H_
>+#ifndef _UAPI_XE_DRM_H_
>+#define _UAPI_XE_DRM_H_
>
> #include "drm.h"
>
>@@ -134,7 +134,7 @@ extern "C" {
> * redefine the interface more easily than an ever growing struct of
> * increasing complexity, and for large parts of that interface to be
> * entirely optional. The downside is more pointer chasing; chasing across
>- * the boundary with pointers encapsulated inside u64.
>+ * the __user boundary with pointers encapsulated inside u64.
> *
> * Example chaining:
> *
>@@ -512,7 +512,9 @@ struct drm_xe_query_gt_list {
> * containing the following in mask:
> * ``DSS_COMPUTE ff ff ff ff 00 00 00 00``
> * means 32 DSS are available for compute.
>- * - %DRM_XE_TOPO_L3_BANK - To query the mask of enabled L3 banks
>+ * - %DRM_XE_TOPO_L3_BANK - To query the mask of enabled L3 banks. This type
>+ * may be omitted if the driver is unable to query the mask from the
>+ * hardware.
> * - %DRM_XE_TOPO_EU_PER_DSS - To query the mask of Execution Units (EU)
> * available per Dual Sub Slices (DSS). For example a query response
> * containing the following in mask:
>@@ -1483,6 +1485,7 @@ struct drm_xe_oa_unit {
> /** @capabilities: OA capabilities bit-mask */
> __u64 capabilities;
> #define DRM_XE_OA_CAPS_BASE (1 << 0)
>+#define DRM_XE_OA_CAPS_SYNCS (1 << 1)
>
> /** @oa_timestamp_freq: OA timestamp freq */
> __u64 oa_timestamp_freq;
>@@ -1632,6 +1635,22 @@ enum drm_xe_oa_property_id {
> * to be disabled for the stream exec queue.
> */
> DRM_XE_OA_PROPERTY_NO_PREEMPT,
>+
>+ /**
>+ * @DRM_XE_OA_PROPERTY_NUM_SYNCS: Number of syncs in the sync array
>+ * specified in @DRM_XE_OA_PROPERTY_SYNCS
>+ */
>+ DRM_XE_OA_PROPERTY_NUM_SYNCS,
>+
>+ /**
>+ * @DRM_XE_OA_PROPERTY_SYNCS: Pointer to struct @drm_xe_sync array
>+ * with array size specified via @DRM_XE_OA_PROPERTY_NUM_SYNCS. OA
>+ * configuration will wait till input fences signal. Output fences
>+ * will signal after the new OA configuration takes effect. For
>+ * @DRM_XE_SYNC_TYPE_USER_FENCE, @addr is a user pointer, similar
>+ * to the VM bind case.
>+ */
>+ DRM_XE_OA_PROPERTY_SYNCS,
> };
>
> /**
>@@ -1698,4 +1717,4 @@ struct drm_xe_oa_stream_info {
> }
> #endif
>
>-#endif /* _XE_DRM_H_ */
>+#endif /* _UAPI_XE_DRM_H_ */
>--
>2.41.0
>
next prev parent reply other threads:[~2024-10-25 19:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-25 18:52 [PATCH i-g-t 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-25 18:52 ` [PATCH i-g-t 1/2] drm-uapi/xe: Sync with OA syncs uapi update Ashutosh Dixit
2024-10-25 19:36 ` Umesh Nerlige Ramappa [this message]
2024-10-28 15:16 ` Kamil Konieczny
2024-10-29 19:38 ` Dixit, Ashutosh
2024-10-25 18:52 ` [PATCH i-g-t 2/2] tests/intel/xe_oa: Tests for OA syncs Ashutosh Dixit
2024-10-25 19:35 ` Umesh Nerlige Ramappa
2024-10-25 19:45 ` Dixit, Ashutosh
2024-10-25 22:02 ` ✓ Fi.CI.BAT: success for tests/intel/oa: Tests for OA syncs (rev4) Patchwork
2024-10-25 22:28 ` ✓ CI.xeBAT: " Patchwork
2024-10-27 12:56 ` ✗ CI.xeFULL: failure " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2024-10-30 2:53 [PATCH i-g-t v5 0/2] tests/intel/oa: Tests for OA syncs Ashutosh Dixit
2024-10-30 2:53 ` [PATCH i-g-t 1/2] drm-uapi/xe: Sync with OA syncs uapi update Ashutosh Dixit
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=ZxvzLU/InQ1Lcjgz@orsosgc001 \
--to=umesh.nerlige.ramappa@intel.com \
--cc=ashutosh.dixit@intel.com \
--cc=igt-dev@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