From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: igt-dev@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915: Return actual submission method from gem_submission_method
Date: Tue, 19 Oct 2021 13:40:22 -0700 [thread overview]
Message-ID: <87lf2oyci1.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <fec8c8fb-aa9e-c657-4b16-2782487df71d@intel.com>
On Tue, 19 Oct 2021 11:19:36 -0700, John Harrison wrote:
>
> On 10/18/2021 20:17, Ashutosh Dixit wrote:
> > gem_submission_method() purports to return the currently used submission
> > method by the driver, as evidenced by its callers. Therefore remove the
> > GEM_SUBMISSION_EXECLISTS flag when GuC submission is detected.
> >
> > This also fixes gem_has_execlists() to match its description, previously
> > gem_has_execlists() would return true even if GuC submission was actually
> > being used in the driver.
>
> The thought occurs that while the behaviour might now match the description
> (and the naming of the underlying flag), the function name really matches
> the old behaviour. Maybe the function should also be renamed to
> gem_has_execlist_submission()? Maybe even rename both to
> gem_using_(execlist|guc)_submission() to be properly accurate?
>
> Or is that just over polishing things?
No I agree, might as well change the names too while we are at it. We could
probably have both _has_ and _using_ but I am not see much use for _has_ so
will probably just keep _using_ as you suggest.
> > diff --git a/tests/i915/gem_ctx_shared.c b/tests/i915/gem_ctx_shared.c
> > index ea1b5dd1b8c..f50ef13263f 100644
> > --- a/tests/i915/gem_ctx_shared.c
> > +++ b/tests/i915/gem_ctx_shared.c
> > @@ -159,7 +159,7 @@ static void disjoint_timelines(int i915, const intel_ctx_cfg_t *cfg)
> > uint32_t plug;
> > uint64_t ahnd;
> > - igt_require(gem_has_execlists(i915));
> > + igt_require(gem_has_execlists(i915) ||
> > gem_has_guc_submission(i915));
>
> I believe Tvrtko is suggesting this one should be a different test entirely:
> > Gem_ctx_shared/disjoint-timlines could perhaps use gem_uses_ppgtt() (for
> create vm)
> > and gem_scheduler_enabled() for context re-ordering
OK, let me go through the mails and see what I come up with in the next
version. Thanks.
next prev parent reply other threads:[~2021-10-19 20:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-19 3:17 [igt-dev] [PATCH i-g-t] lib/i915: Return actual submission method from gem_submission_method Ashutosh Dixit
2021-10-19 4:13 ` [igt-dev] ✓ Fi.CI.BAT: success for lib/i915: Return actual submission method from gem_submission_method (rev2) Patchwork
2021-10-19 5:48 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-10-19 18:19 ` [igt-dev] [PATCH i-g-t] lib/i915: Return actual submission method from gem_submission_method John Harrison
2021-10-19 20:40 ` Dixit, Ashutosh [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-10-16 0:23 Ashutosh Dixit
2021-10-18 23:39 ` John Harrison
2021-10-18 23:59 ` Dixit, Ashutosh
2021-10-19 0:12 ` Dixit, Ashutosh
2021-10-19 7:16 ` John Harrison
2021-10-19 8:39 ` Tvrtko Ursulin
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=87lf2oyci1.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=tvrtko.ursulin@linux.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.