All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>, Dave Gordon <david.s.gordon@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Preallocate request before access of the ring
Date: Mon, 29 Jun 2015 14:39:32 +0300	[thread overview]
Message-ID: <87pp4eyc97.fsf@intel.com> (raw)
In-Reply-To: <20150506100603.GN30184@phenom.ffwll.local>

On Wed, 06 May 2015, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Thu, Apr 30, 2015 at 01:54:41PM +0100, Dave Gordon wrote:
>> On 29/04/15 17:10, yu.dai@intel.com wrote:
>> > From: Alex Dai <yu.dai@intel.com>
>> > 
>> > This is to avoid bad IO access caused by writing NOOP to wrap the
>> > ring buffer whilst ring is unpinned.
>> > 
>> > Signed-off-by: Alex Dai <yu.dai@intel.com>
>> > ---
>> >  drivers/gpu/drm/i915/intel_lrc.c | 6 +++---
>> >  1 file changed, 3 insertions(+), 3 deletions(-)
>> > 
>> > diff --git a/drivers/gpu/drm/i915/intel_lrc.c b/drivers/gpu/drm/i915/intel_lrc.c
>> > index 732fd63..3e8fcfd 100644
>> > --- a/drivers/gpu/drm/i915/intel_lrc.c
>> > +++ b/drivers/gpu/drm/i915/intel_lrc.c
>> > @@ -803,12 +803,12 @@ static int intel_logical_ring_begin(struct intel_ringbuffer *ringbuf,
>> >  	if (ret)
>> >  		return ret;
>> >  
>> > -	ret = logical_ring_prepare(ringbuf, ctx, num_dwords * sizeof(uint32_t));
>> > +	/* Preallocate the olr before touching the ring */
>> > +	ret = i915_gem_request_alloc(ring, ctx);
>> >  	if (ret)
>> >  		return ret;
>> >  
>> > -	/* Preallocate the olr before touching the ring */
>> > -	ret = i915_gem_request_alloc(ring, ctx);
>> > +	ret = logical_ring_prepare(ringbuf, ctx, num_dwords * sizeof(uint32_t));
>> >  	if (ret)
>> >  		return ret;
>> 
>> Reviewed-by: Dave Gordon <david.s.gordon@intel.com>
>> 
>> with input also from John Harrison <john.c.harrison@intel.com>, who
>> would like to point out that this will be superceded by the Anti-OLR
>> patches already posted. (In that model, the request will be allocated
>> much earlier, and passed around explicitly rather than dangling from the
>> context).
>
> Do we need this for execlist in general, i.e. cc: stable? Where's the bug
> report/igt testcase?
>
> For serious-looking bugs please add more details like that to the commit
> message, otherwise maintainers have no idea where to apply a patch.

And due to no reply, the maintainers have forgotten about patches like
this. Dropping from my fixes queue.

BR,
Jani.






>
> Thanks, Daniel
> -- 
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch

-- 
Jani Nikula, Intel Open Source Technology Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-06-29 11:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-29 16:10 [PATCH] drm/i915: Preallocate request before access of the ring yu.dai
2015-04-30 12:54 ` Dave Gordon
2015-05-06 10:06   ` Daniel Vetter
2015-06-29 11:39     ` Jani Nikula [this message]
2015-06-29 13:57       ` Dave Gordon
2015-06-29 14:44         ` Jani Nikula
2015-06-29 15:50           ` Daniel Vetter
2015-05-01  5:59 ` shuang.he

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=87pp4eyc97.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=daniel@ffwll.ch \
    --cc=david.s.gordon@intel.com \
    --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 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.