From: Matthew Brost <matthew.brost@intel.com>
To: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
Cc: <intel-xe@lists.freedesktop.org>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Subject: Re: [PATCH 1/2] drm/xe: Avoid the OOM killer on buffer object memory allocation
Date: Thu, 17 Oct 2024 14:55:16 +0000 [thread overview]
Message-ID: <ZxElVJZJQnx3qCyi@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20241017144407.91919-2-thomas.hellstrom@linux.intel.com>
On Thu, Oct 17, 2024 at 04:44:06PM +0200, Thomas Hellström wrote:
> Rather than invoking the OOM killer on buffer object memory
> allocations and validations, have the allocations fail and
> pass the error to user-space if applicable.
>
> Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> Link: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/2701
> Signed-off-by: Thomas Hellström <thomas.hellstrom@linux.intel.com>
> ---
> drivers/gpu/drm/xe/xe_bo.c | 9 ++++++++-
> 1 file changed, 8 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_bo.c b/drivers/gpu/drm/xe/xe_bo.c
> index c74c121ea7bb..d060f4f019a2 100644
> --- a/drivers/gpu/drm/xe/xe_bo.c
> +++ b/drivers/gpu/drm/xe/xe_bo.c
> @@ -876,6 +876,7 @@ int xe_bo_evict_pinned(struct xe_bo *bo)
> };
> struct ttm_operation_ctx ctx = {
> .interruptible = false,
> + .gfp_retry_mayfail = true,
> };
> struct ttm_resource *new_mem;
> int ret;
> @@ -937,6 +938,7 @@ int xe_bo_restore_pinned(struct xe_bo *bo)
> {
> struct ttm_operation_ctx ctx = {
> .interruptible = false,
> + .gfp_retry_mayfail = false,
> };
> struct ttm_resource *new_mem;
> int ret;
> @@ -1099,7 +1101,8 @@ static void xe_ttm_bo_purge(struct ttm_buffer_object *ttm_bo, struct ttm_operati
> static void xe_ttm_bo_swap_notify(struct ttm_buffer_object *ttm_bo)
> {
> struct ttm_operation_ctx ctx = {
> - .interruptible = false
> + .interruptible = false,
> + .gfp_retry_mayfail = false,
> };
>
> if (ttm_bo->ttm) {
> @@ -1294,6 +1297,7 @@ struct xe_bo *___xe_bo_create_locked(struct xe_device *xe, struct xe_bo *bo,
> struct ttm_operation_ctx ctx = {
> .interruptible = true,
> .no_wait_gpu = false,
> + .gfp_retry_mayfail = true,
> };
> struct ttm_placement *placement;
> uint32_t alignment;
> @@ -1880,6 +1884,7 @@ int xe_bo_validate(struct xe_bo *bo, struct xe_vm *vm, bool allow_res_evict)
> struct ttm_operation_ctx ctx = {
> .interruptible = true,
> .no_wait_gpu = false,
> + .gfp_retry_mayfail = true,
> };
>
> if (vm) {
> @@ -2223,6 +2228,7 @@ int xe_bo_migrate(struct xe_bo *bo, u32 mem_type)
> struct ttm_operation_ctx ctx = {
> .interruptible = true,
> .no_wait_gpu = false,
> + .gfp_retry_mayfail = true,
> };
> struct ttm_placement placement;
> struct ttm_place requested;
> @@ -2273,6 +2279,7 @@ int xe_bo_evict(struct xe_bo *bo, bool force_alloc)
> .interruptible = false,
> .no_wait_gpu = false,
> .force_alloc = force_alloc,
> + .gfp_retry_mayfail = true,
> };
> struct ttm_placement placement;
> int ret;
> --
> 2.46.0
>
next prev parent reply other threads:[~2024-10-17 14:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-17 14:44 [PATCH 0/2] drm/xe: Avoid unnecessary OOM kills Thomas Hellström
2024-10-17 14:44 ` [PATCH 1/2] drm/xe: Avoid the OOM killer on buffer object memory allocation Thomas Hellström
2024-10-17 14:55 ` Matthew Brost [this message]
2024-10-17 14:44 ` [PATCH 2/2] drm/xe: Don't unnecessarily invoke the OOM killer on multiple binds Thomas Hellström
2024-10-17 14:52 ` Matthew Brost
2024-10-17 15:08 ` ✓ CI.Patch_applied: success for drm/xe: Avoid unnecessary OOM kills Patchwork
2024-10-17 15:08 ` ✓ CI.checkpatch: " Patchwork
2024-10-17 15:09 ` ✓ CI.KUnit: " Patchwork
2024-10-17 15:21 ` ✓ CI.Build: " Patchwork
2024-10-17 15:23 ` ✓ CI.Hooks: " Patchwork
2024-10-17 15:24 ` ✓ CI.checksparse: " Patchwork
2024-10-17 15:48 ` ✓ CI.BAT: " Patchwork
2024-10-18 4:39 ` ✗ CI.FULL: 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=ZxElVJZJQnx3qCyi@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=thomas.hellstrom@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