From: Andi Shyti <andi.shyti@linux.intel.com>
To: Nirmoy Das <nirmoy.das@intel.com>
Cc: intel-gfx@lists.freedesktop.org, matthew.auld@intel.com,
chris.p.wilson@intel.com, andrzej.hajda@intel.com
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure
Date: Wed, 27 Jul 2022 22:36:28 +0200 [thread overview]
Message-ID: <YuGhzMYH7vXKIQh4@alfio.lan> (raw)
In-Reply-To: <20220727174023.16766-1-nirmoy.das@intel.com>
Hi Nirmoy,
On Wed, Jul 27, 2022 at 07:40:23PM +0200, Nirmoy Das wrote:
> From: Chris Wilson <chris@chris-wilson.co.uk>
>
> We report object allocation failures to userspace with ENOMEM, yet we
> still show the memory warning after failing to shrink device allocated
> pages. While this warning is similar to other system page allocation
> failures, it is superfluous to the ENOMEM provided directly to
> userspace.
>
> v2: Add NOWARN in few more places from where we might return
> ENOMEM to userspace.
>
> Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/4936
> Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
> Co-developed-by: Nirmoy Das <nirmoy.das@intel.com>
> Signed-off-by: Nirmoy Das <nirmoy.das@intel.com>
Reviewed-by: Andi Shyti <andi.shyti@linux.intel.com>
Andi
next prev parent reply other threads:[~2022-07-27 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 17:40 [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure Nirmoy Das
2022-07-27 19:47 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Suppress oom warning for shmemfs object allocation failure (rev4) Patchwork
2022-07-27 20:18 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-07-27 20:36 ` Andi Shyti [this message]
2022-07-28 8:23 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-07-26 14:47 [Intel-gfx] [PATCH] drm/i915: Suppress oom warning for shmemfs object allocation failure Nirmoy Das
2022-07-26 14:49 ` Das, Nirmoy
2022-07-20 12:23 Nirmoy Das
2022-07-20 12:39 ` Andrzej Hajda
2022-07-21 9:49 ` Matthew Auld
2022-07-21 12:21 ` Das, Nirmoy
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=YuGhzMYH7vXKIQh4@alfio.lan \
--to=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=chris.p.wilson@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=matthew.auld@intel.com \
--cc=nirmoy.das@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.