From: Patchwork <patchwork@emeril.freedesktop.org>
To: "Matthew Brost" <matthew.brost@intel.com>
Cc: intel-xe@lists.freedesktop.org
Subject: [Intel-xe] ✓ CI.Patch_applied: success for USM locking fixes
Date: Tue, 21 Mar 2023 23:44:33 -0000 [thread overview]
Message-ID: <167944227386.18676.4966452263360913411@emeril.freedesktop.org> (raw)
In-Reply-To: <20230321234217.692726-1-matthew.brost@intel.com>
== Series Details ==
Series: USM locking fixes
URL : https://patchwork.freedesktop.org/series/115467/
State : success
== Summary ==
=== Applying kernel patches on branch 'drm-xe-next' with base: ===
commit 1ae4dd9e82429e075aa7121404b06ce170da5848
Author: Matthew Auld <matthew.auld@intel.com>
AuthorDate: Tue Mar 21 11:44:07 2023 +0000
Commit: Matthew Auld <matthew.auld@intel.com>
CommitDate: Tue Mar 21 14:03:29 2023 +0000
drm/xe/buddy: add compatible and intersects hooks
Copy this from i915. We need .compatible for vram -> vram transfers, so
they don't just get nooped by ttm, if need to move something from
mappable to non-mappble or vice versa. The .intersects is needed for
eviction, to determine if a victim resource is worth eviction. e.g if we
need mappable space there is no point in evicting a resource that has
zero mappable pages.
Signed-off-by: Matthew Auld <matthew.auld@intel.com>
Cc: Lucas De Marchi <lucas.demarchi@intel.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
Reviewed-by: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
=== git am output follows ===
Applying: drn/xe: Drop usm lock around ASID xarray
Applying: drm/xe: Move in fault mode / non-fault mode check to xe_vm_create
next prev parent reply other threads:[~2023-03-21 23:44 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-21 23:42 [Intel-xe] [PATCH 0/2] USM locking fixes Matthew Brost
2023-03-21 23:42 ` [Intel-xe] [PATCH 1/2] drn/xe: Drop usm lock around ASID xarray Matthew Brost
2023-03-24 6:17 ` Niranjana Vishwanathapura
2023-03-24 7:19 ` Matthew Brost
2023-03-21 23:42 ` [Intel-xe] [PATCH 2/2] drm/xe: Move in fault mode / non-fault mode check to xe_vm_create Matthew Brost
2023-03-24 6:10 ` Niranjana Vishwanathapura
2023-03-24 7:20 ` Matthew Brost
2023-03-24 16:25 ` Maarten Lankhorst
2023-03-24 16:27 ` Matthew Brost
2023-03-24 16:24 ` Matthew Brost
2023-03-21 23:44 ` Patchwork [this message]
2023-03-21 23:45 ` [Intel-xe] ✓ CI.KUnit: success for USM locking fixes Patchwork
2023-03-21 23:49 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-22 0:13 ` [Intel-xe] ○ CI.BAT: info " 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=167944227386.18676.4966452263360913411@emeril.freedesktop.org \
--to=patchwork@emeril.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=matthew.brost@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.