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 drm/xe: Use fast virtual copy engine for migrate engine on PVC (rev2)
Date: Fri, 24 Mar 2023 01:52:22 -0000 [thread overview]
Message-ID: <167962274293.30854.467608996820296811@emeril.freedesktop.org> (raw)
In-Reply-To: <20230324012329.1195977-1-matthew.brost@intel.com>
== Series Details ==
Series: drm/xe: Use fast virtual copy engine for migrate engine on PVC (rev2)
URL : https://patchwork.freedesktop.org/series/115575/
State : success
== Summary ==
=== Applying kernel patches on branch 'drm-xe-next' with base: ===
commit b21af01dbac717cd5ff86a7b9806225e82e9f323
Author: Matthew Brost <matthew.brost@intel.com>
AuthorDate: Mon Mar 20 13:58:36 2023 -0700
Commit: Matthew Brost <matthew.brost@intel.com>
CommitDate: Thu Mar 23 15:47:07 2023 -0700
drm/xe: Fix potential deadlock handling page faults
Within a class the GuC will hault scheduling if the head of the queue
can't be scheduled the queue will block. This can lead to deadlock if
BCS0-7 all have faults and another engine on BCS0-7 is at head of the
GuC scheduling queue as the migration engine used to fix tthe fault will
be blocked. To work around this set the migration engine to the highest
priority when servicing page faults.
v2 (Maarten): Set priority to kernel once at creation
Signed-off-by: Matthew Brost <matthew.brost@intel.com>
Reviewed-by: Brian Welty <brian.welty@intel.com>
=== git am output follows ===
Applying: drm/xe: Use fast virtual copy engine for migrate engine on PVC
next prev parent reply other threads:[~2023-03-24 1:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 1:23 [Intel-xe] [PATCH v2] drm/xe: Use fast virtual copy engine for migrate engine on PVC Matthew Brost
2023-03-24 1:52 ` Patchwork [this message]
2023-03-24 1:53 ` [Intel-xe] ✓ CI.KUnit: success for drm/xe: Use fast virtual copy engine for migrate engine on PVC (rev2) Patchwork
2023-03-24 1:57 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-03-24 2:19 ` [Intel-xe] ○ CI.BAT: info " Patchwork
2023-03-24 4:53 ` [Intel-xe] [PATCH v2] drm/xe: Use fast virtual copy engine for migrate engine on PVC Lucas De Marchi
2023-03-24 6:59 ` Matthew Brost
2023-03-24 15:29 ` Chang, Yu bruce
2023-03-24 16:07 ` Matthew Brost
2023-03-24 18:12 ` Chang, Yu bruce
2023-03-24 6:42 ` Mauro Carvalho Chehab
2023-03-24 7:02 ` Matthew Brost
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=167962274293.30854.467608996820296811@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.