All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Surendrakumar Upadhyay, TejaskumarX" <tejaskumarx.surendrakumar.upadhyay@intel.com>
To: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: IGT development <igt-dev@lists.freedesktop.org>,
	"Lankhorst, Maarten" <maarten.lankhorst@intel.com>,
	"Ursulin, Tvrtko" <tvrtko.ursulin@intel.com>
Subject: Re: [igt-dev] [i-g-t] tests/gem_userptr_blits: Remove vma-merge subtest
Date: Tue, 31 Aug 2021 05:47:10 +0000	[thread overview]
Message-ID: <SN6PR11MB3421B6569584930A1F603834DFCC9@SN6PR11MB3421.namprd11.prod.outlook.com> (raw)
In-Reply-To: <CAKMK7uEwswaCyEOtEk7rhbXFtSE95+8bUjB+=hjttyStHiMWBQ@mail.gmail.com>



> -----Original Message-----
> From: Daniel Vetter <daniel.vetter@ffwll.ch>
> Sent: 30 August 2021 21:31
> To: Surendrakumar Upadhyay, TejaskumarX
> <tejaskumarx.surendrakumar.upadhyay@intel.com>
> Cc: IGT development <igt-dev@lists.freedesktop.org>; Lankhorst, Maarten
> <maarten.lankhorst@intel.com>; Ursulin, Tvrtko <tvrtko.ursulin@intel.com>
> Subject: Re: [igt-dev] [i-g-t] tests/gem_userptr_blits: Remove vma-merge
> subtest
> 
> On Tue, Aug 24, 2021 at 11:17 AM Tejas Upadhyay
> <tejaskumarx.surendrakumar.upadhyay@intel.com> wrote:
> >
> > mmap requests for huge page size in vma-merge subtest are cancelled
> > from kernel using i915_request_cancel(rq, -EINTR), otherwise it
> > results in system hang. It is known/expected failure thus it is
> > decided to remove the subtest.
> >
> > Signed-off-by: Tejas Upadhyay
> > <tejaskumarx.surendrakumar.upadhyay@intel.com>
> 
> Bugfixes need to link to the gitlab issue, otherwise it's not really a bugfix for a
> CI issue.

Tejas : Ok.

> 
> Furthermore this is wrong:
> - In DII this might happen. If this is a patch upstream then please mark up the
> DII patch as NOT_UPSTREAM. Dropping it is blocked on backporting
> hangcheck. Your manager should be aware of the Jira that tracks hangcheck
> backporting.

Tejas : This is only for upstream. 

> - In upstream hangcheck should get us out of this situation. If not, then this is
> a kernel bug.


Tejas : Hangcheck watchdog is implemented in kernel by Tvrtko. Hence now test does not hang, it fails.

> 
> Cheers, Daniel
> > ---
> >  tests/i915/gem_userptr_blits.c | 40
> > ----------------------------------
> >  1 file changed, 40 deletions(-)
> >
> > diff --git a/tests/i915/gem_userptr_blits.c
> > b/tests/i915/gem_userptr_blits.c index 756bd6e4..11bce6d7 100644
> > --- a/tests/i915/gem_userptr_blits.c
> > +++ b/tests/i915/gem_userptr_blits.c
> > @@ -702,43 +702,6 @@ static size_t hugepagesize(void)  #undef LINE  }
> >
> > -static void test_vma_merge(int i915)
> > -{
> > -       const size_t sz = 2 * hugepagesize();
> > -       igt_spin_t *spin;
> > -       uint32_t handle;
> > -       void *addr;
> > -       uint64_t ahnd = get_reloc_ahnd(i915, 0);
> > -
> > -       addr = mmap(NULL, sz, PROT_READ | PROT_WRITE,
> > -                   MAP_SHARED | MAP_ANONYMOUS, -1, 0);
> > -
> > -       gem_userptr(i915, addr + sz / 2, 4096, 0, userptr_flags, &handle);
> > -
> > -       spin = igt_spin_new(i915, .ahnd = ahnd, .dependency = handle,
> > -                           .flags = IGT_SPIN_FENCE_OUT);
> > -       igt_assert(gem_bo_busy(i915, handle));
> > -
> > -       for (size_t x = 0; x < sz; x += 4096) {
> > -               if (x == sz / 2)
> > -                       continue;
> > -
> > -               igt_assert(mmap(addr + x, 4096, PROT_READ | PROT_WRITE,
> > -                               MAP_FIXED | MAP_SHARED | MAP_ANON, -1, 0) !=
> > -                          MAP_FAILED);
> > -       }
> > -
> > -       igt_spin_end(spin);
> > -       gem_close(i915, handle);
> > -
> > -       munmap(addr, sz);
> > -
> > -       gem_sync(i915, spin->handle);
> > -       igt_assert_eq(sync_fence_status(spin->out_fence), 1);
> > -       igt_spin_free(i915, spin);
> > -       put_ahnd(ahnd);
> > -}
> > -
> >  static void test_huge_split(int i915)  {
> >         const size_t sz = 2 * hugepagesize(); @@ -2614,9 +2577,6 @@
> > igt_main_args("c:", NULL, help_str, opt_handler, NULL)
> >                 igt_subtest("nohangcheck")
> >                         test_nohangcheck_hostile(fd);
> >
> > -               igt_subtest("vma-merge")
> > -                       test_vma_merge(fd);
> > -
> >                 igt_subtest("huge-split")
> >                         test_huge_split(fd);
> >         }
> > --
> > 2.31.1
> >
> 
> 
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

  reply	other threads:[~2021-08-31  5:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-24  9:09 [igt-dev] [i-g-t] tests/gem_userptr_blits: Remove vma-merge subtest Tejas Upadhyay
2021-08-24 14:10 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2021-08-24 17:37 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2021-08-30 16:01 ` [igt-dev] [i-g-t] " Daniel Vetter
2021-08-31  5:47   ` Surendrakumar Upadhyay, TejaskumarX [this message]
2021-08-31 11:36     ` Daniel Vetter
2021-09-07 16:01       ` Surendrakumar Upadhyay, TejaskumarX
2021-09-24  5:23         ` Surendrakumar Upadhyay, TejaskumarX
2021-10-06  9:36           ` Surendrakumar Upadhyay, TejaskumarX

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=SN6PR11MB3421B6569584930A1F603834DFCC9@SN6PR11MB3421.namprd11.prod.outlook.com \
    --to=tejaskumarx.surendrakumar.upadhyay@intel.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=maarten.lankhorst@intel.com \
    --cc=tvrtko.ursulin@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.