From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>,
jani.nikula@linux.intel.com, joonas.lahtinen@linux.intel.com,
rodrigo.vivi@intel.com, airlied@linux.ie, daniel@ffwll.ch,
radhakrishna.sripada@intel.com, ville.syrjala@linux.intel.com,
matthew.d.roper@intel.com, lucas.demarchi@intel.com,
jose.souza@intel.com,
Thomas Hellstrom <thomas.hellstrom@intel.com>,
Matthew Auld <matthew.auld@intel.com>
Cc: intel-gfx@lists.freedesktop.org, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Handle errors for i915_gem_object_trylock
Date: Wed, 2 Mar 2022 10:37:18 +0000 [thread overview]
Message-ID: <9586bba7-ffb8-945f-eb30-88629e34737d@linux.intel.com> (raw)
In-Reply-To: <20220302061946.46630-1-jiasheng@iscas.ac.cn>
+ Thomas, Matt
On 02/03/2022 06:19, Jiasheng Jiang wrote:
> As the potential failure of the i915_gem_object_trylock(),
> it should be better to check it and return error if fails.
>
> Fixes: 94ce0d65076c ("drm/i915/gt: Setup a default migration context on the GT")
> Signed-off-by: Jiasheng Jiang <jiasheng@iscas.ac.cn>
> ---
> drivers/gpu/drm/i915/gt/selftest_migrate.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/i915/gt/selftest_migrate.c b/drivers/gpu/drm/i915/gt/selftest_migrate.c
> index fa4293d2944f..79c6c68f7316 100644
> --- a/drivers/gpu/drm/i915/gt/selftest_migrate.c
> +++ b/drivers/gpu/drm/i915/gt/selftest_migrate.c
> @@ -465,7 +465,11 @@ create_init_lmem_internal(struct intel_gt *gt, size_t sz, bool try_lmem)
> return obj;
> }
>
> - i915_gem_object_trylock(obj, NULL);
Guys why is this a trylock to start with? (Since being added in
94ce0d65076c ("drm/i915/gt: Setup a default migration context on the GT").
Surely it can't ever fail since the object has just been created.
Regards,
Tvrtko
> + if (!i915_gem_object_trylock(obj, NULL)) {
> + i915_gem_object_put(obj);
> + return ERR_PTR(-EBUSY);
> + }
> +
> err = i915_gem_object_pin_pages(obj);
> if (err) {
> i915_gem_object_unlock(obj);
next prev parent reply other threads:[~2022-03-02 10:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 6:19 [Intel-gfx] [PATCH] drm/i915/gt: Handle errors for i915_gem_object_trylock Jiasheng Jiang
2022-03-02 10:37 ` Tvrtko Ursulin [this message]
2022-03-03 10:22 ` Hellstrom, Thomas
2022-03-02 19:01 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2022-03-03 4:38 ` [Intel-gfx] ✗ 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=9586bba7-ffb8-945f-eb30-88629e34737d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=jiasheng@iscas.ac.cn \
--cc=joonas.lahtinen@linux.intel.com \
--cc=jose.souza@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=matthew.auld@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=radhakrishna.sripada@intel.com \
--cc=rodrigo.vivi@intel.com \
--cc=thomas.hellstrom@intel.com \
--cc=ville.syrjala@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox