public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Andi Shyti <andi.shyti@linux.intel.com>
To: Tejas Upadhyay <tejas.upadhyay@intel.com>
Cc: Intel-GFX@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/gt: Consider multi-gt at all places
Date: Mon, 20 Mar 2023 01:24:33 +0100	[thread overview]
Message-ID: <ZBenwTnXPzvjK7WC@ashyti-mobl2.lan> (raw)
In-Reply-To: <20230317055239.1313175-1-tejas.upadhyay@intel.com>

Hi Tejas,

On Fri, Mar 17, 2023 at 11:22:39AM +0530, Tejas Upadhyay wrote:
> In order to make igt_live_test work in proper
> way, we need to consider multi-gt in all tests
> where igt_live_test is used as well as at other
> random places where multi-gt should be considered.
> 
> Cc: Andi Shyti <andi.shyti@linux.intel.com>
> Signed-off-by: Tejas Upadhyay <tejas.upadhyay@intel.com>

Everything looks good, but many things could potentially go wrong
when changing i915 to gt. I would like to see some positive
results from the CI before proceeding.

I will take care of resubmitting the tests once CI is back from
holiday.

Thanks Tejas,
Andi

  parent reply	other threads:[~2023-03-20  0:25 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-17  5:52 [Intel-gfx] [PATCH] drm/i915/gt: Consider multi-gt at all places Tejas Upadhyay
2023-03-17  8:22 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for " Patchwork
2023-03-17  9:16 ` [Intel-gfx] [PATCH] " Tvrtko Ursulin
2023-03-21 23:33   ` Andi Shyti
2023-04-05  6:56   ` Upadhyay, Tejas
2023-04-05  8:30     ` Tvrtko Ursulin
2023-04-17 18:13       ` Upadhyay, Tejas
2023-04-18  7:32         ` Tvrtko Ursulin
2023-03-20  0:24 ` Andi Shyti [this message]
2023-03-21 13:51 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gt: Consider multi-gt at all places (rev2) Patchwork
2023-03-21 23:24   ` Andi Shyti
2023-04-17 20:40 ` [Intel-gfx] ✗ Fi.CI.BUILD: failure for drm/i915/gt: Consider multi-gt at all places (rev3) 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=ZBenwTnXPzvjK7WC@ashyti-mobl2.lan \
    --to=andi.shyti@linux.intel.com \
    --cc=Intel-GFX@lists.freedesktop.org \
    --cc=tejas.upadhyay@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