Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Karolina Stolarek <karolina.stolarek@intel.com>
To: "Zbigniew Kempczyński" <zbigniew.kempczynski@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/xe_vm: Fix missing jiffies -> nanoseconds conversion
Date: Thu, 29 Jun 2023 08:55:29 +0200	[thread overview]
Message-ID: <ed597eb4-9001-688b-17f4-30634c7c8f23@intel.com> (raw)
In-Reply-To: <20230629064807.557491-1-zbigniew.kempczynski@intel.com>


On 29.06.2023 08:48, Zbigniew Kempczyński wrote:
> In the commit 471bfababd070e1dac0ebb87470ac4f2ae85e663 I changed
> timeout granularity from ms -> ns, but I missed one occurence.
> Fix this as we need to want to stop using jiffies in xe wait
> user fence.

Reviewed-by: Karolina Stolarek <karolina.stolarek@intel.com>

> 
> Signed-off-by: Zbigniew Kempczyński <zbigniew.kempczynski@intel.com>
> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
> ---
>   tests/xe/xe_vm.c | 2 +-
>   1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/tests/xe/xe_vm.c b/tests/xe/xe_vm.c
> index 12ecd17fa4..04d6c39568 100644
> --- a/tests/xe/xe_vm.c
> +++ b/tests/xe/xe_vm.c
> @@ -357,7 +357,7 @@ static void *vm_async_ops_err_thread(void *data)
>   		.op = DRM_XE_UFENCE_WAIT_NEQ,
>   		.flags = DRM_XE_UFENCE_WAIT_VM_ERROR,
>   		.mask = DRM_XE_UFENCE_WAIT_U32,
> -		.timeout = 1000,
> +		.timeout = MS_TO_NS(1000),
>   	};
>   
>   	igt_assert_eq(igt_ioctl(fd, DRM_IOCTL_XE_WAIT_USER_FENCE,

  reply	other threads:[~2023-06-29  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-29  6:48 [igt-dev] [PATCH i-g-t] tests/xe_vm: Fix missing jiffies -> nanoseconds conversion Zbigniew Kempczyński
2023-06-29  6:55 ` Karolina Stolarek [this message]
2023-06-29  9:09 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2023-06-29 18:38 ` [igt-dev] ✗ Fi.CI.IGT: failure " 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=ed597eb4-9001-688b-17f4-30634c7c8f23@intel.com \
    --to=karolina.stolarek@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=zbigniew.kempczynski@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