From: Matthew Brost <matthew.brost@intel.com>
To: wangxiaoming321 <xiaoming.wang@intel.com>
Cc: <lucas.demarchi@intel.com>, <ogabbay@kernel.org>,
<thomas.hellstrom@linux.intel.com>,
<maarten.lankhorst@linux.intel.com>, <mripard@kernel.org>,
<tzimmermann@suse.de>, <airlied@gmail.com>, <daniel@ffwll.ch>,
<intel-xe@lists.freedesktop.org>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] drm/xe: Failed getting VMA cause display stuck
Date: Mon, 18 Mar 2024 04:43:12 +0000 [thread overview]
Message-ID: <ZffGYCzt7dUe9Ox9@DUT025-TGLU.fm.intel.com> (raw)
In-Reply-To: <20240318041244.1239610-1-xiaoming.wang@intel.com>
On Mon, Mar 18, 2024 at 12:12:44PM +0800, wangxiaoming321 wrote:
> The failure of binding VMA is duing to interrupt,
> So it needs to retry while return fail.
>
> Signed-off-by: wangxiaoming321 <xiaoming.wang@intel.com>
> ---
> drivers/gpu/drm/xe/xe_vm.c | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/drivers/gpu/drm/xe/xe_vm.c b/drivers/gpu/drm/xe/xe_vm.c
> index 99aa5ffb0ef1..d33476b631e1 100644
> --- a/drivers/gpu/drm/xe/xe_vm.c
> +++ b/drivers/gpu/drm/xe/xe_vm.c
> @@ -2621,6 +2621,9 @@ static int __xe_vma_op_execute(struct xe_vm *vm, struct xe_vma *vma,
> }
> drm_exec_fini(&exec);
>
> + if (err == -ERESTARTSYS)
> + goto retry_userptr;
This doesn't look right. If the user presses ctrl-c we'd restart?
Matt
> +
> if (err == -EAGAIN) {
> lockdep_assert_held_write(&vm->lock);
>
> --
> 2.25.1
>
next prev parent reply other threads:[~2024-03-18 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-18 4:12 [PATCH] drm/xe: Failed getting VMA cause display stuck wangxiaoming321
2024-03-18 4:17 ` ✓ CI.Patch_applied: success for " Patchwork
2024-03-18 4:17 ` ✓ CI.checkpatch: " Patchwork
2024-03-18 4:18 ` ✓ CI.KUnit: " Patchwork
2024-03-18 4:29 ` ✓ CI.Build: " Patchwork
2024-03-18 4:31 ` ✓ CI.Hooks: " Patchwork
2024-03-18 4:33 ` ✓ CI.checksparse: " Patchwork
2024-03-18 4:43 ` Matthew Brost [this message]
2024-03-18 5:23 ` [PATCH] " Matthew Brost
2024-03-18 4:54 ` ✓ CI.BAT: success for " 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=ZffGYCzt7dUe9Ox9@DUT025-TGLU.fm.intel.com \
--to=matthew.brost@intel.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lucas.demarchi@intel.com \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=ogabbay@kernel.org \
--cc=thomas.hellstrom@linux.intel.com \
--cc=tzimmermann@suse.de \
--cc=xiaoming.wang@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