From: Ramalingam C <ramalingam.c@intel.com>
To: "Melkaveri, Arjun" <arjun.melkaveri@intel.com>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t] tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom
Date: Fri, 1 Apr 2022 14:39:45 +0530 [thread overview]
Message-ID: <20220401090945.GB12046@intel.com> (raw)
In-Reply-To: <20220401085507.GA6675@arjun-NUC8i7BEH>
On 2022-04-01 at 14:25:07 +0530, Melkaveri, Arjun wrote:
> On Fri, Apr 01, 2022 at 01:59:28PM +0530, Ramalingam C wrote:
> > On 2022-04-01 at 12:58:26 +0530, Arjun Melkaveri wrote:
> > > ctx was not initialized with all physical engines,
> > > after device reopening.
> > > This change would resolve assert issue seen in __do_evict.
> > >
> > > v2: Added missing intel_ctx_destroy.
> > >
> > > Cc: Ashutosh Dixit <ashutosh.dixit@intel.com>
> > > Cc: Ramalingam C <ramalingam.c@intel.com>
> > > Signed-off-by: Arjun Melkaveri <arjun.melkaveri@intel.com>
> > > ---
> > > tests/i915/gem_lmem_swapping.c | 4 ++++
> > > 1 file changed, 4 insertions(+)
> > >
> > > diff --git a/tests/i915/gem_lmem_swapping.c b/tests/i915/gem_lmem_swapping.c
> > > index 43f0688f..432607b0 100644
> > > --- a/tests/i915/gem_lmem_swapping.c
> > > +++ b/tests/i915/gem_lmem_swapping.c
> > > @@ -428,10 +428,14 @@ static void test_smem_oom(int i915,
> > >
> > > fill_params(i915, ¶ms, region, 0, 1, true);
> > >
> > > + ctx = intel_ctx_create_all_physical(fd);
> > > + __gem_context_set_persistence(fd, ctx->id, false);
> > > +
> > igt fixture already creates same kind of context and pass it here. Could
> > we reuse it across all the child and parent processes?
> >
> > Or we need independed context only?
> >
> > Ram.
> As we are repoening device , this has to be independed context
> "int fd = gem_reopen_driver(i915);"
Ok. Yes got it.
Looks good to me.
Reviewed-by: Ramalingam C <ramalingam.c@intel.com>
> >
> > > igt_install_exit_handler(smem_oom_exit_handler);
> > > __do_evict(fd, ctx, ®ion->region, ¶ms,
> > > params.seed + child + 1);
> > >
> > > + intel_ctx_destroy(fd, ctx);
> > > close(fd);
> > > }
> > >
> > > --
> > > 2.25.1
> > >
next prev parent reply other threads:[~2022-04-01 9:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-01 7:28 [igt-dev] [PATCH i-g-t] tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom Arjun Melkaveri
2022-04-01 7:48 ` [igt-dev] ✗ GitLab.Pipeline: warning for tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom (rev2) Patchwork
2022-04-01 8:15 ` [igt-dev] ✓ Fi.CI.BAT: success " Patchwork
2022-04-01 8:29 ` [igt-dev] [PATCH i-g-t] tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom Ramalingam C
2022-04-01 8:55 ` Melkaveri, Arjun
2022-04-01 9:09 ` Ramalingam C [this message]
2022-04-01 9:10 ` Matthew Auld
2022-04-01 17:52 ` Dixit, Ashutosh
2022-04-01 9:32 ` [igt-dev] ✗ Fi.CI.IGT: failure for tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom (rev2) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2022-04-01 7:25 [igt-dev] [PATCH i-g-t] tests/i915/gem_lmem_swapping: Fix bug in test_smem_oom Arjun Melkaveri
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=20220401090945.GB12046@intel.com \
--to=ramalingam.c@intel.com \
--cc=arjun.melkaveri@intel.com \
--cc=igt-dev@lists.freedesktop.org \
/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