From: "Kumar Valsan, Prathap" <prathap.kumar.valsan@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] [PATCH i-g-t v7] i915/gem_mocs_settings: Add mocs table for icelake
Date: Mon, 18 Mar 2019 09:31:40 -0400 [thread overview]
Message-ID: <20190318133140.GC30702@intel.com> (raw)
In-Reply-To: <155291437385.4168.16028572505368306948@skylake-alporthouse-com>
On Mon, Mar 18, 2019 at 01:06:13PM +0000, Chris Wilson wrote:
> Quoting Kumar Valsan, Prathap (2019-03-18 13:10:43)
> > On Fri, Mar 15, 2019 at 03:15:55PM -0400, Prathap Kumar Valsan wrote:
> > > +static void isolation_test(int fd, unsigned engine)
> > > +{
> > > + uint32_t ctx[2] = { gem_context_create(fd), gem_context_create(fd) };
> > > +
> > > + /* Any writes by one normal client should not affect a second client */
> > > + write_dirty_mocs(fd, engine, ctx[0], false);
> > > + check_mocs_values(fd, engine, ctx[1], false);
> > > +
> > > + for (int i = 0; i < ARRAY_SIZE(ctx); i++)
> > > + gem_context_destroy(fd, ctx[i]);
> > > +}
> > > +
> > > igt_main
> > > {
> > > const struct intel_execution_engine *e;
> > > @@ -490,6 +559,14 @@ igt_main
> > > }
> > > }
> > > }
> > > +
> > > + igt_subtest_f("mocs-isolation-%s",
> > > + e->name) {
> > > + gem_require_contexts(fd);
> > > +
> > > + isolation_test(fd, e->exec_id | e->flags);
> > > + }
> > > +
> > > }
> > Chris,
> > Added isolation_test as a subtest. Can i get a r-b if this looks good to
> > you.
>
> Yup, that looks like what I expect we need to verify the ABI that mocs
> values are independent without overburdening ourselves with actual HW
> implementation.
>
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
> -Chris
Thanks for the reviews.
-Prathap
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-03-18 13:17 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-15 21:46 [igt-dev] [PATCH i-g-t] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan via igt-dev
2019-02-15 22:48 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev3) Patchwork
2019-02-16 6:07 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-20 8:33 ` [igt-dev] [PATCH i-g-t] i915/gem_mocs_settings: Add mocs table for icelake Szwichtenberg, Radoslaw
2019-02-21 22:48 ` Lucas De Marchi
2019-02-21 23:42 ` Chris Wilson
2019-02-22 17:49 ` Lucas De Marchi
2019-02-22 14:05 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev4) Patchwork
2019-02-22 14:17 ` [igt-dev] [PATCH i-g-t v2] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-02-22 15:17 ` Lis, Tomasz
2019-02-22 15:21 ` Chris Wilson
2019-02-22 21:32 ` Kumar Valsan, Prathap
2019-02-22 21:48 ` Chris Wilson
2019-02-25 13:17 ` Lis, Tomasz
2019-02-25 0:26 ` Kumar Valsan, Prathap
2019-02-22 21:16 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev5) Patchwork
2019-02-22 21:20 ` [igt-dev] [PATCH i-g-t v3] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-04 20:27 ` [igt-dev] [PATCH i-g-t v4] " Prathap Kumar Valsan
2019-03-04 20:37 ` Kumar Valsan, Prathap
2019-03-04 21:01 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev6) Patchwork
2019-03-05 2:11 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-03-12 15:14 ` [igt-dev] [PATCH i-g-t v5] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-13 13:58 ` Kalamarz, Lukasz
2019-03-14 9:18 ` Chris Wilson
2019-03-14 11:03 ` Kalamarz, Lukasz
2019-03-13 12:12 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev7) Patchwork
2019-03-14 0:12 ` [igt-dev] [PATCH i-g-t v5] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-14 0:47 ` [igt-dev] ✗ Fi.CI.BAT: failure for i915/gem_mocs_settings: Add mocs table for icelake (rev8) Patchwork
2019-03-14 17:28 ` [igt-dev] [PATCH i-g-t v6] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-15 8:46 ` Chris Wilson
2019-03-15 19:28 ` Kumar Valsan, Prathap
2019-03-15 21:11 ` Chris Wilson
2019-03-14 18:07 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev9) Patchwork
2019-03-15 2:54 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-03-15 19:15 ` [igt-dev] [PATCH i-g-t v7] i915/gem_mocs_settings: Add mocs table for icelake Prathap Kumar Valsan
2019-03-18 13:10 ` Kumar Valsan, Prathap
2019-03-18 13:06 ` Chris Wilson
2019-03-18 13:31 ` Kumar Valsan, Prathap [this message]
2019-03-18 13:27 ` Chris Wilson
2019-03-18 10:21 ` [igt-dev] ✓ Fi.CI.BAT: success for i915/gem_mocs_settings: Add mocs table for icelake (rev11) Patchwork
2019-03-18 12:37 ` [igt-dev] ✓ Fi.CI.IGT: " 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=20190318133140.GC30702@intel.com \
--to=prathap.kumar.valsan@intel.com \
--cc=chris@chris-wilson.co.uk \
--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