From: "Thomas Hellström" <thomas.hellstrom@linux.intel.com>
To: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
intel-xe@lists.freedesktop.org
Subject: Re: [Intel-xe] [PATCH 2/5] drm/xe: Add debugfs files to evict everything.
Date: Tue, 30 May 2023 16:41:06 +0200 [thread overview]
Message-ID: <6cd54420-f374-c796-940f-807ddadd6f43@linux.intel.com> (raw)
In-Reply-To: <678c272b-97dc-f556-4403-96c2f895fa9b@linux.intel.com>
On 5/29/23 15:35, Maarten Lankhorst wrote:
> Hey,
>
> On 2023-05-26 15:02, Thomas Hellström wrote:
>> On 5/26/23 14:10, Maarten Lankhorst wrote:
>>> Easy for testing, when you just want your BO evicted.
>>>
>>> Signed-off-by: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
>> Do we have some documentation somewhere about what our debugfs entries are doing that needs updating?
> I've not seen any documentation for those specific debugfs entries.
>> Also can we evict stolen memory?
> What is useful to evict? I think all of our users of stolen memory only use it pinned.
What I meant was, assuming that we have evictable stolen memory, can
xe_bo_move() handle it properly, even when accessed as system /ggtt? If
not, should we ditch the debugfs entry for stolen for now?
/Thomas
>
> ~Maarten
>
next prev parent reply other threads:[~2023-05-30 14:41 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 12:10 [Intel-xe] [PATCH 0/5] Robustness fixes with eviction and invalidation Maarten Lankhorst
2023-05-26 12:10 ` [Intel-xe] [PATCH 1/5] drm/xe: Kill small race with userptr invalidation Maarten Lankhorst
2023-05-26 12:26 ` Thomas Hellström
2023-05-26 12:10 ` [Intel-xe] [PATCH 2/5] drm/xe: Add debugfs files to evict everything Maarten Lankhorst
2023-05-26 13:02 ` Thomas Hellström
2023-05-29 13:35 ` Maarten Lankhorst
2023-05-30 14:41 ` Thomas Hellström [this message]
2023-05-30 14:54 ` Maarten Lankhorst
2023-05-26 12:10 ` [Intel-xe] [PATCH 3/5] drm/xe: Fix extobj dropping issue Maarten Lankhorst
2023-05-26 12:31 ` Thomas Hellström
2023-05-26 12:11 ` [Intel-xe] [PATCH 4/5] drm/xe: Prevent evicting for page tables Maarten Lankhorst
2023-05-26 12:35 ` Thomas Hellström
2023-05-29 13:44 ` Maarten Lankhorst
2023-05-29 15:02 ` Thomas Hellström
2023-05-29 15:11 ` Maarten Lankhorst
2023-05-29 15:13 ` Thomas Hellström
2023-05-29 15:23 ` Maarten Lankhorst
2023-05-30 8:45 ` Thomas Hellström
2023-05-30 8:50 ` Maarten Lankhorst
2023-05-26 12:11 ` [Intel-xe] [PATCH 5/5] drm/xe: Return the correct error when dma_resv_wait_timeout fails Maarten Lankhorst
2023-05-26 12:40 ` Thomas Hellström
2023-05-26 19:15 ` Souza, Jose
2023-05-27 5:17 ` Christopher Snowhill
2023-05-29 15:21 ` Maarten Lankhorst
2023-05-26 12:13 ` [Intel-xe] ✓ CI.Patch_applied: success for Robustness fixes with eviction and invalidation Patchwork
2023-05-26 12:15 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-05-26 12:19 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-05-26 12:48 ` [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=6cd54420-f374-c796-940f-807ddadd6f43@linux.intel.com \
--to=thomas.hellstrom@linux.intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=maarten.lankhorst@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 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.