All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Auld <matthew.auld@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gem: Differentiate oom failures from invalid map types
Date: Mon, 30 Nov 2020 13:24:36 +0000	[thread overview]
Message-ID: <099bfb02-f13e-4bab-659f-c3e847aeeed3@intel.com> (raw)
In-Reply-To: <20201127195334.13134-1-chris@chris-wilson.co.uk>

On 27/11/2020 19:53, Chris Wilson wrote:
> After a cursory check on the parameters to i915_gem_object_pin_map(),
> where we return a precise error, if the backend rejects the mapping we
> always return PTR_ERR(-ENOMEM). Let us also return a more precise error
> here so we can differentiate between running out of memory and
> programming errors (or situations where we may be trying different paths
> and looking for an error from an unsupported map).
> 
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Matthew Auld <matthew.auld@intel.com>
Reviewed-by: Matthew Auld <matthew.auld@intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2020-11-30 13:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-27 19:53 [Intel-gfx] [PATCH] drm/i915/gem: Differentiate oom failures from invalid map types Chris Wilson
2020-11-27 21:39 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-11-28  0:11 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
2020-11-30 13:24 ` Matthew Auld [this message]

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=099bfb02-f13e-4bab-659f-c3e847aeeed3@intel.com \
    --to=matthew.auld@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@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 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.