All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Goel, Akash" <akash.goel@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Cc: akash.goel@intel.com
Subject: Re: [PATCH 08/19] drm/i915: Add a relay backed debugfs interface for capturing GuC logs
Date: Sat, 20 Aug 2016 12:10:15 +0530	[thread overview]
Message-ID: <534115c7-fd92-5b4c-d080-6455156d84a7@intel.com> (raw)
In-Reply-To: <20160819180341.GA16497@nuc-i3427.alporthouse.com>



On 8/19/2016 11:33 PM, Chris Wilson wrote:
> On Fri, Aug 19, 2016 at 02:13:07PM +0530, akash.goel@intel.com wrote:
>>  static void *guc_get_write_buffer(struct intel_guc *guc)
>>  {
>> -	return NULL;
>> +	/* FIXME: Cover the check under a lock ? */
>> +	if (!guc->log.relay_chan)
>> +		return NULL;
>> +
>> +	/* Just get the base address of a new sub buffer and copy data into it
>> +	 * ourselves. NULL will be returned in no-overwrite mode, if all sub
>> +	 * buffers are full. Could have used the relay_write() to indirectly
>> +	 * copy the data, but that would have been bit convoluted, as we need to
>> +	 * write to only certain locations inside a sub buffer which cannot be
>> +	 * done without using relay_reserve() along with relay_write(). So its
>> +	 * better to use relay_reserve() alone.
>> +	 */
>> +	return relay_reserve(guc->log.relay_chan, 0);
>>  }
>
> You have to chase through the code a long way to check whether or not
> the allocation is correct.
>
> Please do consider adding a check such as
>
> 	GEM_BUG_ON(guc->log.relay_chan->size < guc->log.vma->size);
> (near the allocation)

Fine, will add a check after the allocation, but not sure how useful it
will be, as we shall trust relay to do the memory allocation for the
sub-buffers as per the requested 'subbuf_size'.

subbuf_size = guc->log.vma->obj->base.size;
n_subbufs = 8;
guc_log_relay_chan = relay_open(NULL, NULL, subbuf_size,
				n_subbufs, &relay_callbacks, dev_priv);


GEM_BUG_ON(guc->log.relay_chan->subbuf_size < guc->log.vma->obj->base.size);


>
> 	GEM_BUG_ON(write_offset + buffer_size > guc->log.relay_chan->size);
> (before the memcpy, or whatever is appropriate).
>
There is a check already for read_offset/write_offset before the memcpy.

I think it would be better to add this check
GEM_BUG_ON(guc->log.relay_chan->subbuf_size < guc->log.vma->obj->base.size);

just before
return relay_reserve(guc->log.relay_chan, 0);

Best regards
Akash

> Just to leave some clues to the reader as to what is going on.
> -Chris
>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2016-08-20  6:40 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19  8:42 [PATCH v8 00/19] Support for sustained capturing of GuC firmware logs akash.goel
2016-08-19  8:43 ` [PATCH 01/19] drm/i915: Decouple GuC log setup from verbosity parameter akash.goel
2016-08-19  8:43 ` [PATCH 02/19] drm/i915: Add GuC ukernel logging related fields to fw interface file akash.goel
2016-08-19  8:43 ` [PATCH 03/19] drm/i915: New structure to contain GuC logging related fields akash.goel
2016-08-19  8:43 ` [PATCH 04/19] drm/i915: Add low level set of routines for programming PM IER/IIR/IMR register set akash.goel
2016-08-19  8:43 ` [PATCH 05/19] drm/i915: Support for GuC interrupts akash.goel
2016-08-19  8:43 ` [PATCH 06/19] drm/i915: Handle log buffer flush interrupt event from GuC akash.goel
2016-08-19 10:08   ` Tvrtko Ursulin
2016-08-19  8:43 ` [PATCH 07/19] relay: Use per CPU constructs for the relay channel buffer pointers akash.goel
2016-08-19  8:43 ` [PATCH 08/19] drm/i915: Add a relay backed debugfs interface for capturing GuC logs akash.goel
2016-08-19 18:03   ` Chris Wilson
2016-08-20  6:40     ` Goel, Akash [this message]
2016-08-19  8:43 ` [PATCH 09/19] drm/i915: New lock to serialize the Host2GuC actions akash.goel
2016-08-19  8:43 ` [PATCH 10/19] drm/i915: Add stats for GuC log buffer flush interrupts akash.goel
2016-08-19  8:43 ` [PATCH 11/19] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 12/19] drm/i915: Increase GuC log buffer size to reduce flush interrupts akash.goel
2016-08-19  8:43 ` [PATCH 13/19] drm/i915: Augment i915 error state to include the dump of GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 14/19] drm/i915: Forcefully flush GuC log buffer on reset akash.goel
2016-08-19 18:10   ` Chris Wilson
2016-08-20  6:49     ` Goel, Akash
2016-08-19  8:43 ` [PATCH 15/19] drm/i915: Debugfs support for GuC logging control akash.goel
2016-08-19 18:18   ` Chris Wilson
2016-08-20  6:40     ` Goel, Akash
2016-08-19  8:43 ` [PATCH 16/19] drm/i915: Use uncached(WC) mapping for acessing the GuC log buffer akash.goel
2016-08-19  8:43 ` [PATCH 17/19] drm/i915: Use SSE4.1 movntdqa based memcpy for sampling " akash.goel
2016-08-19 18:19   ` Chris Wilson
2016-08-20  6:44     ` Goel, Akash
2016-08-20  8:40       ` Chris Wilson
2016-08-19  8:43 ` [PATCH 18/19] drm/i915: Early creation of relay channel for capturing boot time logs akash.goel
2016-08-19  8:43 ` [PATCH 19/19] drm/i915: Mark the GuC log buffer flush interrupts handling WQ as freezable akash.goel
2016-08-19 10:19   ` Imre Deak
2016-08-19  9:01 ` ✗ Ro.CI.BAT: failure for Support for sustained capturing of GuC firmware logs (rev9) Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2016-08-17 10:14 [PATCH v7 00/19] Support for sustained capturing of GuC firmware logs akash.goel
2016-08-17 10:14 ` [PATCH 08/19] drm/i915: Add a relay backed debugfs interface for capturing GuC logs akash.goel
2016-08-17 11:11   ` Tvrtko Ursulin

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=534115c7-fd92-5b4c-d080-6455156d84a7@intel.com \
    --to=akash.goel@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 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.