From: "Dixit, Ashutosh" <ashutosh.dixit@intel.com>
To: John Harrison <john.c.harrison@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t 1/3] lib/i915: Return actual submission method from gem_submission_method
Date: Tue, 02 Nov 2021 15:48:53 -0700 [thread overview]
Message-ID: <87v91akwbu.wl-ashutosh.dixit@intel.com> (raw)
In-Reply-To: <871r3ymknq.wl-ashutosh.dixit@intel.com>
On Tue, 02 Nov 2021 12:18:01 -0700, Dixit, Ashutosh wrote:
>
> I think I am going to do this. Also, has_semaphores() calls here in i915:
>
> int i915_getparam_ioctl()
> {
> ...
> case I915_PARAM_HAS_SEMAPHORES:
> value = !!(i915->caps.scheduler & I915_SCHEDULER_CAP_SEMAPHORES);
> break;
>
> But appears I915_SCHEDULER_CAP_SEMAPHORES bits are never set in
> caps.scheduler so has_semaphores() should always be returning zero.
Sorry I am wrong, I915_SCHEDULER_CAP_SEMAPHORES is set in i915
set_scheduler_caps() and gem_busy@semaphores tests run in CI.
next prev parent reply other threads:[~2021-11-02 22:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 4:40 [igt-dev] [PATCH i-g-t 0/3] Return actual submission methods from submission method functions Ashutosh Dixit
2021-10-28 4:40 ` [igt-dev] [PATCH i-g-t 1/3] lib/i915: Return actual submission method from gem_submission_method Ashutosh Dixit
2021-10-28 23:55 ` John Harrison
2021-10-29 0:31 ` Dixit, Ashutosh
2021-10-30 0:42 ` John Harrison
2021-11-02 19:18 ` Dixit, Ashutosh
2021-11-02 22:48 ` Dixit, Ashutosh [this message]
2021-10-28 4:40 ` [igt-dev] [PATCH i-g-t 2/3] lib/i915: Clarify gem_submission function names Ashutosh Dixit
2021-10-28 4:40 ` [igt-dev] [PATCH i-g-t 3/3] tests/gem_ctx_shared: Fix disjoint_timelines test requirements Ashutosh Dixit
2021-10-28 5:15 ` [igt-dev] ✓ Fi.CI.BAT: success for Return actual submission methods from submission method functions Patchwork
2021-10-28 9:20 ` [igt-dev] ✓ Fi.CI.IGT: " 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=87v91akwbu.wl-ashutosh.dixit@intel.com \
--to=ashutosh.dixit@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=john.c.harrison@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.