From: Stuart Summers <stuart.summers@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/3] drm/i915: Use render class for MI_SET_CONTEXT
Date: Tue, 13 Aug 2019 11:00:18 -0700 [thread overview]
Message-ID: <1565719218.30036.41.camel@intel.com> (raw)
In-Reply-To: <156571886655.2301.17809116448263908293@skylake-alporthouse-com>
On Tue, 2019-08-13 at 18:54 +0100, Chris Wilson wrote:
> Quoting Stuart Summers (2019-08-13 18:41:19)
> > Replace GEM_BUG_ON with explicit check for render class
> > when doing the kernel context switch.
> >
> > Signed-off-by: Stuart Summers <stuart.summers@intel.com>
> > ---
> > drivers/gpu/drm/i915/gt/intel_ringbuffer.c | 4 +---
> > 1 file changed, 1 insertion(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/gt/intel_ringbuffer.c
> > b/drivers/gpu/drm/i915/gt/intel_ringbuffer.c
> > index 409d764f8c6d..04ea9bbb88ce 100644
> > --- a/drivers/gpu/drm/i915/gt/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/gt/intel_ringbuffer.c
> > @@ -1781,9 +1781,7 @@ static int switch_context(struct i915_request
> > *rq)
> > }
> > }
> >
> > - if (rq->hw_context->state) {
> > - GEM_BUG_ON(engine->id != RCS0);
> > -
> > + if (engine->class == RENDER_CLASS && rq->hw_context->state)
> > {
>
> It would come as some surprise for this not to be rcs0. I don't think
> we
> are prepared for that on legacy HW :)
Heh, I will admit that this isn't a strict requirement but thought it
would be nice to have. If you're opposed we can drop this.
Thanks,
Stuart
> -Chris
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-08-13 17:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-13 17:41 [PATCH 1/3] drm/i915: Use render class for MI_SET_CONTEXT Stuart Summers
2019-08-13 17:41 ` [PATCH 2/3] drm/i915: Print CCID for all renderCS Stuart Summers
2019-08-13 17:55 ` Chris Wilson
2019-08-14 9:02 ` Chris Wilson
2019-08-14 21:59 ` Stuart Summers
2019-08-13 17:41 ` [PATCH 3/3] drm/i915: Add module parameter to remove RCS engine Stuart Summers
2019-08-13 18:03 ` Chris Wilson
2019-08-13 18:11 ` Chris Wilson
2019-08-13 17:54 ` [PATCH 1/3] drm/i915: Use render class for MI_SET_CONTEXT Chris Wilson
2019-08-13 18:00 ` Stuart Summers [this message]
2019-08-13 18:05 ` Chris Wilson
2019-08-13 18:41 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/3] " Patchwork
2019-08-13 19:03 ` ✓ Fi.CI.BAT: success " Patchwork
2019-08-14 6:03 ` ✗ Fi.CI.IGT: failure " 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=1565719218.30036.41.camel@intel.com \
--to=stuart.summers@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@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