From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: John Harrison <john.c.harrison@intel.com>,
igt-dev@lists.freedesktop.org,
Zbigniew Kempczynski <zbigniew.kempczynski@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/i915: Fix gem_has_execlists to match description
Date: Mon, 18 Oct 2021 15:11:31 -0700 [thread overview]
Message-ID: <87fssy7zl8.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <784e8917-05cc-c5ed-ef98-dc21edda789b@linux.intel.com>
On Mon, 18 Oct 2021 00:43:10 -0700, Tvrtko Ursulin wrote:
>
> >>> Don't we use ring submission on older platforms?
> >> Hmm, I wasn't aware that there was yet another submission method :/
> >>
> >> So execlist submission is only available for gen >= 8 as the code says,
> >> in
> >> case anyone knows?
> > Yes. Execlists was new feature of the hardware not all that long ago
> > (ELSP and all that). Gen8 sounds plausible.
>
> Yes Gen8+.
>
> > Of course, it all depends why the code is asking the question? Does it
> > really need to know what the submission hardware is? Or is it actually
> > asking about the scheduling algorithm (as is the case for
> > gem_exec_fair). Or something else entirely? The scheduler question is
> > going to change again when we move to using the DRM scheduler instead of
> > our own private one in the execlist code. Currently though, I would
> > assume we use the execlist scheduler for ring submission but certainly
> > not for GuC submission (because the scheduler is in the hardware).
>
> Nope, no scheduling with ringbuffer backend.
>
> There is I915_PARAM_HAS_SCHEDULER and respective IGT helpers to query what
> kind of scheduling is supported on the device in question.
>
> It will be on a test per test basis why it is asking the question and what
> would be the appropriate test.
This patch is abandoned in favor of:
https://patchwork.freedesktop.org/series/95906/
Would it be possible to get a review on that? Thanks.
next prev parent reply other threads:[~2021-10-18 22:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-15 23:38 [igt-dev] [PATCH i-g-t] lib/i915: Fix gem_has_execlists to match description Ashutosh Dixit
2021-10-15 23:33 ` Dixit, Ashutosh
2021-10-15 23:42 ` John Harrison
2021-10-15 23:39 ` Dixit, Ashutosh
2021-10-15 23:57 ` John Harrison
2021-10-18 7:43 ` Tvrtko Ursulin
2021-10-18 22:11 ` Dixit, Ashutosh [this message]
2021-10-18 23:40 ` John Harrison
2021-10-19 8:53 ` Tvrtko Ursulin
2021-10-19 18:08 ` John Harrison
2021-10-16 0:50 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-10-16 5:00 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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=87fssy7zl8.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 \
--cc=zbigniew.kempczynski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox