From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 103107] [CI] igt@gem_ctx_param@invalid-param-[get|set] - Failed assertion: __gem_context_get_param(fd, &arg) == -22
Date: Thu, 11 Jan 2018 11:26:54 +0000 [thread overview]
Message-ID: <bug-103107-502-MEDaS3MUFN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103107-502@http.bugs.freedesktop.org/>
[-- Attachment #1.1: Type: text/plain, Size: 1304 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=103107
--- Comment #10 from Marta Löfstedt <marta.lofstedt@intel.com> ---
I believe this issue started when the I915_CONTEXT_PARAM_PRIORITY was added.
commit ac14fbd460d0ec16e7750e40dcd8199b0ff83d0a
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date: Tue Oct 3 21:34:53 2017 +0100
drm/i915/scheduler: Support user-defined priorities
so instead of hitting default case with -EINVAL return, in
i915_gem_context_getparam_ioctl, I915_CONTEXT_PARAM_BANNABLE + 1 gives us
I915_CONTEXT_PARAM_PRIORITY.
So, we could just change I915_CONTEXT_PARAM_BANNABLE + 1 to
I915_CONTEXT_PARAM_PRIORITY + 1, but there is a comment in the testcase:
/* NOTE: This testcase intentionally tests for the next free parameter
* to catch ABI extensions. Don't "fix" this testcase without adding all
* the tests for the new param first.
*/
As strict interpretation of this gives that subtest for the missing
I915_CONTEXT_PARAM_GTT_SIZE, I915_CONTEXT_PARAM_NO_ERROR_CAPTURE,
I915_CONTEXT_PARAM_BANNABLE and I915_CONTEXT_PARAM_PRIORITY, needs to be added
before changing this test. I.e. this testcase fails because there are niot
testcases for all context params.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2306 bytes --]
[-- Attachment #2: Type: text/plain, Size: 160 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2018-01-11 11:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-103107-502@http.bugs.freedesktop.org/>
2017-10-05 8:48 ` [Bug 103107] [CI] igt@gem_ctx_param@invalid-param-[get|set] - Failed assertion: __gem_context_get_param(fd, &arg) == -22 bugzilla-daemon
2017-10-11 9:42 ` bugzilla-daemon
2017-10-18 11:31 ` bugzilla-daemon
2017-11-08 9:04 ` bugzilla-daemon
2017-11-17 20:57 ` bugzilla-daemon
2017-11-21 10:44 ` bugzilla-daemon
2017-11-29 20:12 ` bugzilla-daemon
2017-11-30 16:41 ` bugzilla-daemon
2017-12-21 21:18 ` bugzilla-daemon
2018-01-11 11:26 ` bugzilla-daemon [this message]
2018-01-11 11:38 ` bugzilla-daemon
2018-01-29 18:46 ` bugzilla-daemon
2018-02-15 7:28 ` bugzilla-daemon
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=bug-103107-502-MEDaS3MUFN@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/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