From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: akash.goel@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 11/18] drm/i915: Optimization to reduce the sampling time of GuC log buffer
Date: Mon, 15 Aug 2016 16:36:40 +0100 [thread overview]
Message-ID: <57B1E188.40406@linux.intel.com> (raw)
In-Reply-To: <1471272599-14586-12-git-send-email-akash.goel@intel.com>
On 15/08/16 15:49, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> GuC firmware sends an interrupt to flush the log buffer when it becomes
> half full, so Driver doesn't really need to sample the complete buffer
> and can just copy only the newly written data by GuC into the local
> buffer, i.e. as per the read & write pointer values.
> Moreover the flush interrupt would generally come for one type of log
> buffer, when it becomes half full, so at that time the other 2 types of
> log buffer would comparatively have much lesser unread data in them.
> In case of overflow reported by GuC, Driver do need to copy the entire
> buffer as the whole buffer would contain the unread data.
>
> v2: Rebase.
>
> v3: Fix the blooper of doing the copy twice. (Tvrtko)
>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
> drivers/gpu/drm/i915/i915_guc_submission.c | 40 +++++++++++++++++++++++++-----
> 1 file changed, 34 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/i915_guc_submission.c b/drivers/gpu/drm/i915/i915_guc_submission.c
> index c7b4a57..b8d6313 100644
> --- a/drivers/gpu/drm/i915/i915_guc_submission.c
> +++ b/drivers/gpu/drm/i915/i915_guc_submission.c
> @@ -1003,6 +1003,8 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> void *src_data_ptr, *dst_data_ptr;
> unsigned int buffer_size, expected_size;
> enum guc_log_buffer_type type;
> + unsigned int read_offset, write_offset, bytes_to_copy;
> + bool new_overflow;
>
> if (WARN_ON(!guc->log.buf_addr))
> return;
> @@ -1025,11 +1027,14 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> memcpy(&log_buffer_state_local, log_buffer_state,
> sizeof(struct guc_log_buffer_state));
> buffer_size = log_buffer_state_local.size;
> + read_offset = log_buffer_state_local.read_ptr;
> + write_offset = log_buffer_state_local.sampled_write_ptr;
>
> /* Bookkeeping stuff */
> guc->log.flush_count[type] += log_buffer_state_local.flush_to_file;
> if (log_buffer_state_local.buffer_full_cnt !=
> guc->log.prev_overflow_count[type]) {
> + new_overflow = 1;
> guc->log.total_overflow_count[type] +=
> (log_buffer_state_local.buffer_full_cnt -
> guc->log.prev_overflow_count[type]);
> @@ -1043,7 +1048,8 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> guc->log.prev_overflow_count[type] =
> log_buffer_state_local.buffer_full_cnt;
> DRM_ERROR_RATELIMITED("GuC log buffer overflow\n");
> - }
> + } else
> + new_overflow = 0;
Nitpick: normally the rule is if one branch has curlies all of them have
to. Checkpatch I think warns about that, or maybe only in strict mode.
>
> if (log_buffer_snapshot_state) {
> /* First copy the state structure in snapshot buffer */
> @@ -1055,8 +1061,7 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> * for consistency set the write pointer value to same
> * value of sampled_write_ptr in the snapshot buffer.
> */
> - log_buffer_snapshot_state->write_ptr =
> - log_buffer_snapshot_state->sampled_write_ptr;
> + log_buffer_snapshot_state->write_ptr = write_offset;
>
> log_buffer_snapshot_state++;
>
> @@ -1079,7 +1084,31 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> buffer_size = expected_size;
> }
>
> - memcpy(dst_data_ptr, src_data_ptr, buffer_size);
> + if (unlikely(new_overflow)) {
> + /* copy the whole buffer in case of overflow */
> + read_offset = 0;
> + write_offset = buffer_size;
> + } else if (unlikely((read_offset > buffer_size) ||
> + (write_offset > buffer_size))) {
Could also check for read_offset == write_offset for even more safety?
> + DRM_ERROR("invalid log buffer state\n");
> + /* copy whole buffer as offsets are unreliable */
> + read_offset = 0;
> + write_offset = buffer_size;
> + }
> +
> + /* Just copy the newly written data */
> + if (read_offset <= write_offset) {
> + bytes_to_copy = write_offset - read_offset;
> + memcpy(dst_data_ptr + read_offset,
> + src_data_ptr + read_offset, bytes_to_copy);
> + } else {
> + bytes_to_copy = buffer_size - read_offset;
> + memcpy(dst_data_ptr + read_offset,
> + src_data_ptr + read_offset, bytes_to_copy);
> +
> + bytes_to_copy = write_offset;
> + memcpy(dst_data_ptr, src_data_ptr, bytes_to_copy);
> + }
>
> src_data_ptr += buffer_size;
> dst_data_ptr += buffer_size;
> @@ -1088,8 +1117,7 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> /* FIXME: invalidate/flush for log buffer needed */
>
> /* Update the read pointer in the shared log buffer */
> - log_buffer_state->read_ptr =
> - log_buffer_state_local.sampled_write_ptr;
> + log_buffer_state->read_ptr = write_offset;
>
> /* Clear the 'flush to file' flag */
> log_buffer_state->flush_to_file = 0;
>
Looks OK to me.
Reviewed-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-08-15 15:36 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-15 14:49 [PATCH v6 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-08-15 14:49 ` [PATCH 01/18] drm/i915: Decouple GuC log setup from verbosity parameter akash.goel
2016-08-15 14:49 ` [PATCH 02/18] drm/i915: Add GuC ukernel logging related fields to fw interface file akash.goel
2016-08-15 14:49 ` [PATCH 03/18] drm/i915: New structure to contain GuC logging related fields akash.goel
2016-08-15 14:49 ` [PATCH 04/18] drm/i915: Add low level set of routines for programming PM IER/IIR/IMR register set akash.goel
2016-08-15 14:49 ` [PATCH 05/18] drm/i915: Support for GuC interrupts akash.goel
2016-08-15 14:54 ` Tvrtko Ursulin
2016-08-15 14:49 ` [PATCH 06/18] drm/i915: Handle log buffer flush interrupt event from GuC akash.goel
2016-08-15 15:20 ` Tvrtko Ursulin
2016-08-15 15:57 ` Goel, Akash
2016-08-15 16:06 ` Chris Wilson
2016-08-15 16:46 ` Goel, Akash
2016-08-15 16:56 ` Chris Wilson
2016-08-16 5:37 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 07/18] relay: Use per CPU constructs for the relay channel buffer pointers akash.goel
2016-08-15 14:49 ` [PATCH 08/18] drm/i915: Add a relay backed debugfs interface for capturing GuC logs akash.goel
2016-08-15 15:29 ` Tvrtko Ursulin
2016-08-15 16:02 ` Goel, Akash
2016-08-15 16:09 ` Chris Wilson
2016-08-15 16:12 ` Chris Wilson
2016-08-15 16:38 ` Goel, Akash
2016-08-15 16:47 ` Chris Wilson
2016-08-15 14:49 ` [PATCH 09/18] drm/i915: New lock to serialize the Host2GuC actions akash.goel
2016-08-15 14:49 ` [PATCH 10/18] drm/i915: Add stats for GuC log buffer flush interrupts akash.goel
2016-08-15 14:49 ` [PATCH 11/18] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
2016-08-15 15:36 ` Tvrtko Ursulin [this message]
2016-08-15 16:13 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 12/18] drm/i915: Increase GuC log buffer size to reduce flush interrupts akash.goel
2016-08-15 14:49 ` [PATCH 13/18] drm/i915: Augment i915 error state to include the dump of GuC log buffer akash.goel
2016-08-15 15:39 ` Tvrtko Ursulin
2016-08-15 14:49 ` [PATCH 14/18] drm/i915: Forcefully flush GuC log buffer on reset akash.goel
2016-08-15 15:48 ` Tvrtko Ursulin
2016-08-16 5:25 ` Goel, Akash
2016-08-16 9:25 ` Tvrtko Ursulin
2016-08-16 9:39 ` Goel, Akash
2016-08-16 9:42 ` Tvrtko Ursulin
2016-08-16 11:27 ` Tvrtko Ursulin
2016-08-16 12:19 ` Goel, Akash
2016-08-15 14:49 ` [PATCH 15/18] drm/i915: Debugfs support for GuC logging control akash.goel
2016-08-15 16:03 ` Tvrtko Ursulin
2016-08-15 14:49 ` [PATCH 16/18] drm/i915: Use uncached(WC) mapping for acessing the GuC log buffer akash.goel
2016-08-15 14:49 ` [PATCH 17/18] drm/i915: Use SSE4.1 movntdqa based memcpy for sampling " akash.goel
2016-08-15 14:49 ` [PATCH 18/18] drm/i915: Early creation of relay channel for capturing boot time logs akash.goel
2016-08-15 15:59 ` Tvrtko Ursulin
2016-08-15 15:10 ` ✗ Ro.CI.BAT: failure for Support for sustained capturing of GuC firmware logs (rev7) Patchwork
-- strict thread matches above, loose matches on Subject: below --
2016-09-08 10:39 [PATCH v9 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-09-08 10:39 ` [PATCH 11/18] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
2016-10-12 16:24 [PATCH v10 00/18] Support for sustained capturing of GuC firmware logs akash.goel
2016-10-12 16:24 ` [PATCH 11/18] drm/i915: Optimization to reduce the sampling time of GuC log buffer akash.goel
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=57B1E188.40406@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=akash.goel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox