From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: "Cavitt, Jonathan" <jonathan.cavitt@intel.com>
Cc: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>,
"Nerlige Ramappa, Umesh" <umesh.nerlige.ramappa@intel.com>
Subject: Re: [PATCH] drm/xe/oa/uapi: Expose an unblock after N reports OA property
Date: Fri, 13 Dec 2024 09:19:30 -0800 [thread overview]
Message-ID: <85bjxf33h9.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <CH0PR11MB5444E1D6E5A1F98473B67743E53F2@CH0PR11MB5444.namprd11.prod.outlook.com>
On Thu, 12 Dec 2024 14:59:35 -0800, Cavitt, Jonathan wrote:
>
> > diff --git a/drivers/gpu/drm/xe/xe_query.c b/drivers/gpu/drm/xe/xe_query.c
> > index d2a816f71bf26..226b234d07110 100644
> > --- a/drivers/gpu/drm/xe/xe_query.c
> > +++ b/drivers/gpu/drm/xe/xe_query.c
> > @@ -672,7 +672,7 @@ static int query_oa_units(struct xe_device *xe,
> > du->oa_unit_type = u->type;
> > du->oa_timestamp_freq = xe_oa_timestamp_frequency(gt);
> > du->capabilities = DRM_XE_OA_CAPS_BASE | DRM_XE_OA_CAPS_SYNCS |
> > - DRM_XE_OA_CAPS_OA_BUFFER_SIZE;
> > + DRM_XE_OA_CAPS_OA_BUFFER_SIZE | DRM_XE_OA_CAPS_WAIT_NUM_REPORTS;
>
> This should probably be kept inline:
> """
> du->capabilities = DRM_XE_OA_CAPS_BASE | DRM_XE_OA_CAPS_SYNCS |
> DRM_XE_OA_CAPS_OA_BUFFER_SIZE |
> DRM_XE_OA_CAPS_WAIT_NUM_REPORTS;
> """
> But otherwise:
> Reviewed-by: Jonathan Cavitt <jonathan.cavitt@intel.com>
Thanks, sure I will make this change.
Also the MDAPI UMD PR for this kernel change is:
https://github.com/intel/metrics-discovery/pull/32
Thanks.
--
Ashutosh
> > j = 0;
> > for_each_hw_engine(hwe, gt, hwe_id) {
> > diff --git a/include/uapi/drm/xe_drm.h b/include/uapi/drm/xe_drm.h
> > index 0383b52cbd869..f62689ca861a4 100644
> > --- a/include/uapi/drm/xe_drm.h
> > +++ b/include/uapi/drm/xe_drm.h
> > @@ -1487,6 +1487,7 @@ struct drm_xe_oa_unit {
> > #define DRM_XE_OA_CAPS_BASE (1 << 0)
> > #define DRM_XE_OA_CAPS_SYNCS (1 << 1)
> > #define DRM_XE_OA_CAPS_OA_BUFFER_SIZE (1 << 2)
> > +#define DRM_XE_OA_CAPS_WAIT_NUM_REPORTS (1 << 3)
> >
> > /** @oa_timestamp_freq: OA timestamp freq */
> > __u64 oa_timestamp_freq;
> > @@ -1660,6 +1661,12 @@ enum drm_xe_oa_property_id {
> > * buffer is allocated by default.
> > */
> > DRM_XE_OA_PROPERTY_OA_BUFFER_SIZE,
> > +
> > + /**
> > + * @DRM_XE_OA_PROPERTY_WAIT_NUM_REPORTS: Number of reports to wait
> > + * for before unblocking poll or read
> > + */
> > + DRM_XE_OA_PROPERTY_WAIT_NUM_REPORTS,
> > };
> >
> > /**
> > --
> > 2.47.1
> >
> >
next prev parent reply other threads:[~2024-12-13 17:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-12 22:49 [PATCH] drm/xe/oa/uapi: Expose an unblock after N reports OA property Ashutosh Dixit
2024-12-12 22:59 ` Cavitt, Jonathan
2024-12-13 17:19 ` Dixit, Ashutosh [this message]
2024-12-12 23:10 ` ✓ CI.Patch_applied: success for " Patchwork
2024-12-12 23:10 ` ✗ CI.checkpatch: warning " Patchwork
2024-12-12 23:11 ` ✓ CI.KUnit: success " Patchwork
2024-12-12 23:38 ` ✓ CI.Build: " Patchwork
2024-12-12 23:42 ` ✓ CI.Hooks: " Patchwork
2024-12-12 23:45 ` ✓ CI.checksparse: " Patchwork
2024-12-13 0:12 ` ✓ Xe.CI.BAT: " Patchwork
2024-12-13 7:03 ` ✗ Xe.CI.Full: failure " Patchwork
2024-12-14 0:54 ` [PATCH] " Umesh Nerlige Ramappa
2024-12-14 1:08 ` Dixit, Ashutosh
2024-12-16 22:48 ` Umesh Nerlige Ramappa
2024-12-17 2:17 ` Dixit, Ashutosh
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=85bjxf33h9.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=jonathan.cavitt@intel.com \
--cc=umesh.nerlige.ramappa@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.