From: Daniel Vetter <daniel@ffwll.ch> To: Matthew Brost <matthew.brost@intel.com> Cc: tony.ye@intel.com, tvrtko.ursulin@intel.com, intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, carl.zhang@intel.com, jason.ekstrand@intel.com, daniele.ceraolospurio@intel.com, jon.bloomfield@intel.com, daniel.vetter@intel.com, john.c.harrison@intel.com Subject: Re: [RFC PATCH 3/5] drm/i915: Expose logical engine instance to user Date: Tue, 11 May 2021 16:53:34 +0200 [thread overview] Message-ID: <YJqabmnUEjwi8iAJ@phenom.ffwll.local> (raw) In-Reply-To: <20210506173049.72503-4-matthew.brost@intel.com> On Thu, May 06, 2021 at 10:30:47AM -0700, Matthew Brost wrote: > Expose logical engine instance to user via query engine info IOCTL. This > is required for split-frame workloads as these need to be placed on > engines in a logically contiguous order. The logical mapping can change > based on fusing. Rather than having user have knowledge of the fusing we > simply just expose the logical mapping with the existing query engine > info IOCTL. > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Cc: Tony Ye <tony.ye@intel.com> > CC: Carl Zhang <carl.zhang@intel.com> > Cc: Daniel Vetter <daniel.vetter@intel.com> > Cc: Jason Ekstrand <jason@jlekstrand.net> > Signed-off-by: Matthew Brost <matthew.brost@intel.com> > --- > include/uapi/drm/i915_drm.h | 7 ++++++- Two things on all these 3 patches: - Until we've merged the uapi it shouldn't show up in uapi headers. See what Matt A. has done with a fake local header in Documentation/gpu/rfc which you can pull in. - Since this one is tiny I think just the text in the rfc is good enough, I'd drop this. - Squash the others in with the parallel submit rfc patch so that the structs and long-form text are all in one patch please, makes reviewing the overall thing a bit simpler. Rule is to have a complete change per patch, and then not split things further. > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h > index 9f331ad629f5..26d2e135aa31 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -2396,14 +2396,19 @@ struct drm_i915_engine_info { > > /** @flags: Engine flags. */ > __u64 flags; > +#define I915_ENGINE_INFO_HAS_LOGICAL_INSTANCE (1 << 0) > > /** @capabilities: Capabilities of this engine. */ > __u64 capabilities; > #define I915_VIDEO_CLASS_CAPABILITY_HEVC (1 << 0) > #define I915_VIDEO_AND_ENHANCE_CLASS_CAPABILITY_SFC (1 << 1) > > + /** Logical engine instance */ I think in the final version that we merge with the uapi this should: - explain why we need this - link to relevant other uapi like the paralle submit extension Cheers, Daniel > + __u16 logical_instance; > + > /** @rsvd1: Reserved fields. */ > - __u64 rsvd1[4]; > + __u16 rsvd1[3]; > + __u64 rsvd2[3]; > }; > > /** > -- > 2.28.0 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch
WARNING: multiple messages have this Message-ID (diff)
From: Daniel Vetter <daniel@ffwll.ch> To: Matthew Brost <matthew.brost@intel.com> Cc: intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, carl.zhang@intel.com, jason.ekstrand@intel.com, daniel.vetter@intel.com Subject: Re: [Intel-gfx] [RFC PATCH 3/5] drm/i915: Expose logical engine instance to user Date: Tue, 11 May 2021 16:53:34 +0200 [thread overview] Message-ID: <YJqabmnUEjwi8iAJ@phenom.ffwll.local> (raw) In-Reply-To: <20210506173049.72503-4-matthew.brost@intel.com> On Thu, May 06, 2021 at 10:30:47AM -0700, Matthew Brost wrote: > Expose logical engine instance to user via query engine info IOCTL. This > is required for split-frame workloads as these need to be placed on > engines in a logically contiguous order. The logical mapping can change > based on fusing. Rather than having user have knowledge of the fusing we > simply just expose the logical mapping with the existing query engine > info IOCTL. > > Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> > Cc: Tony Ye <tony.ye@intel.com> > CC: Carl Zhang <carl.zhang@intel.com> > Cc: Daniel Vetter <daniel.vetter@intel.com> > Cc: Jason Ekstrand <jason@jlekstrand.net> > Signed-off-by: Matthew Brost <matthew.brost@intel.com> > --- > include/uapi/drm/i915_drm.h | 7 ++++++- Two things on all these 3 patches: - Until we've merged the uapi it shouldn't show up in uapi headers. See what Matt A. has done with a fake local header in Documentation/gpu/rfc which you can pull in. - Since this one is tiny I think just the text in the rfc is good enough, I'd drop this. - Squash the others in with the parallel submit rfc patch so that the structs and long-form text are all in one patch please, makes reviewing the overall thing a bit simpler. Rule is to have a complete change per patch, and then not split things further. > 1 file changed, 6 insertions(+), 1 deletion(-) > > diff --git a/include/uapi/drm/i915_drm.h b/include/uapi/drm/i915_drm.h > index 9f331ad629f5..26d2e135aa31 100644 > --- a/include/uapi/drm/i915_drm.h > +++ b/include/uapi/drm/i915_drm.h > @@ -2396,14 +2396,19 @@ struct drm_i915_engine_info { > > /** @flags: Engine flags. */ > __u64 flags; > +#define I915_ENGINE_INFO_HAS_LOGICAL_INSTANCE (1 << 0) > > /** @capabilities: Capabilities of this engine. */ > __u64 capabilities; > #define I915_VIDEO_CLASS_CAPABILITY_HEVC (1 << 0) > #define I915_VIDEO_AND_ENHANCE_CLASS_CAPABILITY_SFC (1 << 1) > > + /** Logical engine instance */ I think in the final version that we merge with the uapi this should: - explain why we need this - link to relevant other uapi like the paralle submit extension Cheers, Daniel > + __u16 logical_instance; > + > /** @rsvd1: Reserved fields. */ > - __u64 rsvd1[4]; > + __u16 rsvd1[3]; > + __u64 rsvd2[3]; > }; > > /** > -- > 2.28.0 > -- Daniel Vetter Software Engineer, Intel Corporation http://blog.ffwll.ch _______________________________________________ Intel-gfx mailing list Intel-gfx@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2021-05-11 14:53 UTC|newest] Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-06 17:30 [RFC PATCH 0/5] GuC submission / DRM scheduler integration plan + new uAPI Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-06 17:27 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for " Patchwork 2021-05-06 17:30 ` [RFC PATCH 1/5] drm/doc/rfc: i915 GuC submission / DRM scheduler integration plan Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-11 14:34 ` Daniel Vetter 2021-05-11 14:34 ` Daniel Vetter 2021-05-11 14:58 ` Daniel Stone 2021-05-11 14:58 ` Daniel Stone 2021-05-11 15:12 ` Daniel Vetter 2021-05-11 15:12 ` Daniel Vetter 2021-05-06 17:30 ` [RFC PATCH 2/5] drm/doc/rfc: i915 new parallel submission uAPI plan Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-11 14:49 ` Daniel Vetter 2021-05-11 14:49 ` Daniel Vetter 2021-05-11 17:51 ` Matthew Brost 2021-05-11 17:51 ` Matthew Brost 2021-05-06 17:30 ` [RFC PATCH 3/5] drm/i915: Expose logical engine instance to user Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-11 14:53 ` Daniel Vetter [this message] 2021-05-11 14:53 ` Daniel Vetter 2021-05-06 17:30 ` [RFC PATCH 4/5] drm/i915: Introduce 'set parallel submit' extension Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-11 15:11 ` Daniel Vetter 2021-05-11 15:11 ` Daniel Vetter 2021-05-11 18:44 ` Matthew Brost 2021-05-11 18:44 ` Matthew Brost 2021-05-12 8:34 ` Daniel Vetter 2021-05-12 8:34 ` Daniel Vetter 2021-05-14 20:05 ` Matthew Brost 2021-05-14 20:05 ` Matthew Brost 2021-05-17 13:55 ` Daniel Vetter 2021-05-17 13:55 ` Daniel Vetter 2021-05-17 17:46 ` Matthew Brost 2021-05-17 17:46 ` Matthew Brost 2021-05-06 17:30 ` [RFC PATCH 5/5] drm/i915: Update execbuf IOCTL to accept N BBs Matthew Brost 2021-05-06 17:30 ` [Intel-gfx] " Matthew Brost 2021-05-11 15:13 ` Daniel Vetter 2021-05-11 15:13 ` Daniel Vetter 2021-05-11 18:01 ` Matthew Brost 2021-05-11 18:01 ` Matthew Brost
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=YJqabmnUEjwi8iAJ@phenom.ffwll.local \ --to=daniel@ffwll.ch \ --cc=carl.zhang@intel.com \ --cc=daniel.vetter@intel.com \ --cc=daniele.ceraolospurio@intel.com \ --cc=dri-devel@lists.freedesktop.org \ --cc=intel-gfx@lists.freedesktop.org \ --cc=jason.ekstrand@intel.com \ --cc=john.c.harrison@intel.com \ --cc=jon.bloomfield@intel.com \ --cc=matthew.brost@intel.com \ --cc=tony.ye@intel.com \ --cc=tvrtko.ursulin@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: linkBe 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.