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>,
Michal Wajdeczko <michal.wajdeczko@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915: Return actual submission method from gem_submission_method
Date: Mon, 18 Oct 2021 16:59:43 -0700 [thread overview]
Message-ID: <87czo1995c.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <15873c81-caec-c822-867f-7f0392606126@intel.com>
On Mon, 18 Oct 2021 16:39:40 -0700, John Harrison wrote:
>
> On 10/15/2021 17:23, 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.
> >
> > Reported-by: John Harrison <john.c.harrison@intel.com>
> > Cc: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
> > Signed-off-by: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > ---
> > lib/i915/gem_submission.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/lib/i915/gem_submission.c b/lib/i915/gem_submission.c
> > index 2627b802cfb..b037d04cc4a 100644
> > --- a/lib/i915/gem_submission.c
> > +++ b/lib/i915/gem_submission.c
> > @@ -86,7 +86,7 @@ unsigned gem_submission_method(int fd)
> > return 0;
> > if (igt_sysfs_get_u32(dir, "enable_guc") & 1) {
> > - flags |= GEM_SUBMISSION_GUC | GEM_SUBMISSION_EXECLISTS;
> > + flags |= GEM_SUBMISSION_GUC;
> > goto out;
> > }
> >
> Looks good to me, but as per the comments in the other thread, this might
> have unintended side effects. Have you gone through all instances of the
> submission query usages to check how it is used and whether this will break
> something? E.g. if something is explicitly testing for execlist support to
> mean 'something better than ring buffer' then it would now fail.
There are at present just these two instances of gem_has_execlists:
*** tests/i915/gem_ctx_shared.c:
disjoint_timelines[162] igt_require(gem_has_execlists(i915));
*** tests/i915/gem_watchdog.c:
virtual[225] igt_require(gem_has_execlists(i915));
I'll try to see if I can figure out if they will be affected in any
way. Meanwhile since Tvrtko seems to have authored/reviewed these tests, if
he can chime in that would be great :) Thanks!
next prev parent reply other threads:[~2021-10-18 23:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-16 0:23 [igt-dev] [PATCH i-g-t] lib/i915: Return actual submission method from gem_submission_method Ashutosh Dixit
2021-10-16 1:19 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-16 5:45 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2021-10-18 23:39 ` [igt-dev] [PATCH i-g-t] " John Harrison
2021-10-18 23:59 ` Dixit, Ashutosh [this message]
2021-10-19 0:12 ` Dixit, Ashutosh
2021-10-19 7:16 ` John Harrison
2021-10-19 8:39 ` Tvrtko Ursulin
-- strict thread matches above, loose matches on Subject: below --
2021-10-19 3:17 Ashutosh Dixit
2021-10-19 18:19 ` John Harrison
2021-10-19 20:40 ` 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=87czo1995c.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@intel.com \
--cc=michal.wajdeczko@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.