All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915/selftests: Verify whitelist of context registers
Date: Wed, 24 Apr 2019 12:03:52 +0100	[thread overview]
Message-ID: <155610383229.19502.12508638103825220969@skylake-alporthouse-com> (raw)
In-Reply-To: <155610000320.19502.11596492856166711018@skylake-alporthouse-com>

Quoting Chris Wilson (2019-04-24 11:00:03)
> Quoting Tvrtko Ursulin (2019-04-16 15:50:27)
> > 
> > On 16/04/2019 10:12, Chris Wilson wrote:
> > > +     rq = ERR_PTR(-ENODEV);
> > > +     with_intel_runtime_pm(engine->i915, wakeref)
> > > +             rq = i915_request_alloc(engine, ctx);
> > > +     if (IS_ERR(rq))
> > > +             goto err_unpin;
> > > +
> > > +     if (engine->emit_init_breadcrumb) { /* Be nice if we hang */
> > > +             err = engine->emit_init_breadcrumb(rq);
> > > +             if (err)
> > > +                     goto err_request;
> > > +     }
> > > +
> > > +     err = engine->emit_bb_start(rq, batch->node.start, 0, 0);
> > 
> > Why is batch needed here when everything else is happy to run from the ring?
> 
> Because we are playing with HW registers, I want reset to work safely.
> So long as we have init_breadcrumb, the payload scrubbing should work.
> Ok.

No, I am an idiot. The batch is so that we emulate userspace with
unprivileged execution
-Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-04-24 11:03 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-16  8:10 [PATCH v2 1/4] drm/i915: Verify workarounds immediately after application Chris Wilson
2019-04-16  8:10 ` [PATCH v2 2/4] drm/i915: Verify the engine workarounds stick on application Chris Wilson
2019-04-16  9:43   ` Tvrtko Ursulin
2019-04-16  9:57     ` Chris Wilson
2019-04-16 10:36       ` Tvrtko Ursulin
2019-04-16 10:49         ` Chris Wilson
2019-04-16  8:10 ` [PATCH v2 3/4] drm/i915: Make workaround verification *optional* Chris Wilson
2019-04-16  9:48   ` Tvrtko Ursulin
2019-04-16 11:24     ` Chris Wilson
2019-04-16  8:10 ` [PATCH v2 4/4] drm/i915/selftests: Verify whitelist of context registers Chris Wilson
2019-04-16  9:12   ` [PATCH] " Chris Wilson
2019-04-16 14:50     ` Tvrtko Ursulin
2019-04-24 10:00       ` Chris Wilson
2019-04-24 11:03         ` Chris Wilson [this message]
2019-04-24 11:10           ` Tvrtko Ursulin
2019-04-16 21:28   ` [PATCH v2 4/4] " kbuild test robot
2019-04-16  9:18 ` [PATCH v2 1/4] drm/i915: Verify workarounds immediately after application Tvrtko Ursulin
2019-04-16 11:10 ` ✓ Fi.CI.BAT: success for series starting with [v2,1/4] drm/i915: Verify workarounds immediately after application (rev2) Patchwork
2019-04-16 15:07 ` ✓ Fi.CI.IGT: " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2019-04-15 16:00 [PATCH 4/4] drm/i915/selftests: Verify whitelist of context registers Chris Wilson
2019-04-15 17:41 ` [PATCH] " Chris Wilson

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=155610383229.19502.12508638103825220969@skylake-alporthouse-com \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=tvrtko.ursulin@linux.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.