From: Francois Dugast <francois.dugast@intel.com>
To: <priyanka.dandamudi@intel.com>
Cc: <igt-dev@lists.freedesktop.org>
Subject: Re: [PATCH i-g-t] lib/intel_compute.c : Increase WMTP loop count
Date: Tue, 25 Mar 2025 09:51:40 +0100 [thread overview]
Message-ID: <Z-JunHtuZWtgVRgp@fdugast-desk> (raw)
In-Reply-To: <20250325052901.195938-1-priyanka.dandamudi@intel.com>
Hi Priyanka,
On Tue, Mar 25, 2025 at 10:59:01AM +0530, priyanka.dandamudi@intel.com wrote:
> From: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
>
> Preemption is not happening and getting failed at the check for long
> kernel with current WMTP loop count. So, increasing the loop count.
>
> Signed-off-by: Priyanka Dandamudi <priyanka.dandamudi@intel.com>
> ---
> lib/intel_compute.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/lib/intel_compute.c b/lib/intel_compute.c
> index 28149db53..76d435794 100644
> --- a/lib/intel_compute.c
> +++ b/lib/intel_compute.c
> @@ -52,7 +52,7 @@
> * WMTP - Walker Mid Thread Preemption
> */
> #define TGP_long_kernel_loop_count 10
> -#define WMTP_long_kernel_loop_count 1000000
> +#define WMTP_long_kernel_loop_count 1500000
I am still observing sporadic issues in compute-preempt-many with this
new value, but not with 2000000.
Francois
>
> struct bo_dict_entry {
> uint64_t addr;
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-03-25 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 5:29 [PATCH i-g-t] lib/intel_compute.c : Increase WMTP loop count priyanka.dandamudi
2025-03-25 6:25 ` ✓ Xe.CI.BAT: success for " Patchwork
2025-03-25 6:33 ` ✗ i915.CI.BAT: failure " Patchwork
2025-03-25 8:51 ` Francois Dugast [this message]
2025-03-25 13:54 ` [PATCH i-g-t] " Dandamudi, Priyanka
2025-03-25 12:02 ` Kamil Konieczny
-- strict thread matches above, loose matches on Subject: below --
2025-03-25 13:58 priyanka.dandamudi
2025-03-28 8:40 ` Francois Dugast
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=Z-JunHtuZWtgVRgp@fdugast-desk \
--to=francois.dugast@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=priyanka.dandamudi@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.