From: Matthew Brost <matthew.brost@intel.com>
To: Brian Welty <brian.welty@intel.com>
Cc: igt-dev@lists.freedesktop.org, Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [igt-dev] [PATCH i-g-t] lib/xe_query: Fix xe_supports_faults()
Date: Wed, 6 Dec 2023 18:29:37 +0000 [thread overview]
Message-ID: <ZXC9kYXvhGehJJa7@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20231207012623.15901-1-brian.welty@intel.com>
On Wed, Dec 06, 2023 at 05:26:23PM -0800, Brian Welty wrote:
> In recent uAPI changes, it was missed that setting VM_CREATE_FLAG_FAULT_MODE
> requires VM_CREATE_FLAG_LR_MODE in this query routine.
>
> Fixes: dc71419700 (tests/intel/xe: Adjust to KMD uAPI changes for long-running VMs)
> Closes: https://gitlab.freedesktop.org/drm/xe/kernel/-/issues/997
> Signed-off-by: Brian Welty <brian.welty@intel.com>
Reviewed-by: Matthew Brost <matthew.brost@intel.com>
> ---
> lib/xe/xe_query.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/lib/xe/xe_query.c b/lib/xe/xe_query.c
> index 3ebce83615..701fe1d1ea 100644
> --- a/lib/xe/xe_query.c
> +++ b/lib/xe/xe_query.c
> @@ -312,6 +312,7 @@ bool xe_supports_faults(int fd)
>
> struct drm_xe_vm_create create = {
> .flags = DRM_XE_VM_CREATE_FLAG_ASYNC_DEFAULT |
> + DRM_XE_VM_CREATE_FLAG_LR_MODE |
> DRM_XE_VM_CREATE_FLAG_FAULT_MODE,
> };
>
> --
> 2.38.0
>
next prev parent reply other threads:[~2023-12-07 1:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 1:26 [igt-dev] [PATCH i-g-t] lib/xe_query: Fix xe_supports_faults() Brian Welty
2023-12-06 18:29 ` Matthew Brost [this message]
2023-12-07 2:40 ` [igt-dev] ✗ Fi.CI.BAT: failure for " Patchwork
2023-12-07 11:33 ` Kamil Konieczny
2023-12-13 6:59 ` Musial, Ewelina
2023-12-13 8:33 ` Illipilli, TejasreeX
2023-12-07 3:26 ` [igt-dev] ✓ CI.xeBAT: success " Patchwork
2023-12-13 8:27 ` ✓ Fi.CI.BAT: " Patchwork
2023-12-13 8:28 ` Patchwork
2023-12-13 10:15 ` ✗ Fi.CI.IGT: failure " Patchwork
2023-12-14 7:26 ` ✓ Fi.CI.IGT: success " 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=ZXC9kYXvhGehJJa7@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=brian.welty@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=rodrigo.vivi@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