From: Sagar Arun Kamble <sagar.a.kamble@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>,
intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 06/15] drm/i915/guc: Merge log relay file and channel creation
Date: Mon, 5 Mar 2018 17:14:03 +0530 [thread overview]
Message-ID: <f4f46576-c568-60c5-01b0-eedd74df771b@intel.com> (raw)
In-Reply-To: <20180227125230.13000-6-michal.winiarski@intel.com>
On 2/27/2018 6:22 PM, Michał Winiarski wrote:
> We have all the information we need at relay_open call time.
> Since there's no reason to split the process into relay_open and
> relay_late_setup_files, let's remove the extra code.
>
> Signed-off-by: Michał Winiarski <michal.winiarski@intel.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Cc: Daniele Ceraolo Spurio <daniele.ceraolospurio@intel.com>
> Cc: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> Cc: Michal Wajdeczko <michal.wajdeczko@intel.com>
Looks good to me. Comment updates needed.
With that:
Reviewed-by: Sagar Arun Kamble <sagar.a.kamble@intel.com>
> ---
> drivers/gpu/drm/i915/intel_guc_log.c | 52 ++++--------------------------------
> 1 file changed, 5 insertions(+), 47 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/intel_guc_log.c b/drivers/gpu/drm/i915/intel_guc_log.c
> index 567620464f52..cbbdb400fa17 100644
> --- a/drivers/gpu/drm/i915/intel_guc_log.c
> +++ b/drivers/gpu/drm/i915/intel_guc_log.c
> @@ -126,7 +126,7 @@ static struct dentry *create_buf_file_callback(const char *filename,
> * dentry of the file associated with the channel buffer and that file's
> * name need not be same as the filename passed as an argument.
> */
Need to update comment as we are using channel filename now.
> - buf_file = debugfs_create_file("guc_log", mode,
> + buf_file = debugfs_create_file(filename, mode,
> parent, buf, &relay_file_operations);
> return buf_file;
> }
> @@ -147,43 +147,6 @@ static struct rchan_callbacks relay_callbacks = {
> .remove_buf_file = remove_buf_file_callback,
> };
>
> -static int guc_log_relay_file_create(struct intel_guc *guc)
> -{
> - struct drm_i915_private *dev_priv = guc_to_i915(guc);
> - struct dentry *log_dir;
> - int ret;
> -
> - lockdep_assert_held(&guc->log.runtime.lock);
> -
> - /* For now create the log file in /sys/kernel/debug/dri/0 dir */
> - log_dir = dev_priv->drm.primary->debugfs_root;
> -
> - /*
> - * If /sys/kernel/debug/dri/0 location do not exist, then debugfs is
> - * not mounted and so can't create the relay file.
> - * The relay API seems to fit well with debugfs only, for availing relay
> - * there are 3 requirements which can be met for debugfs file only in a
> - * straightforward/clean manner :-
> - * i) Need the associated dentry pointer of the file, while opening the
> - * relay channel.
> - * ii) Should be able to use 'relay_file_operations' fops for the file.
> - * iii) Set the 'i_private' field of file's inode to the pointer of
> - * relay channel buffer.
> - */
> - if (!log_dir) {
> - DRM_ERROR("Debugfs dir not available yet for GuC log file\n");
> - return -ENODEV;
> - }
> -
> - ret = relay_late_setup_files(guc->log.runtime.relay_chan, "guc_log", log_dir);
> - if (ret < 0 && ret != -EEXIST) {
> - DRM_ERROR("Couldn't associate relay chan with file %d\n", ret);
> - return ret;
> - }
> -
> - return 0;
> -}
> -
> static void guc_move_to_next_buf(struct intel_guc *guc)
> {
> /*
> @@ -267,7 +230,6 @@ static void guc_read_update_log_buffer(struct intel_guc *guc)
> /* Get the pointer to shared GuC log buffer */
> log_buf_state = src_data = guc->log.runtime.buf_addr;
>
> -
> /* Get the pointer to local buffer to store the logs */
> log_buf_snapshot_state = dst_data = guc_get_write_buffer(guc);
>
> @@ -436,8 +398,10 @@ int guc_log_relay_create(struct intel_guc *guc)
> * the GuC firmware logs, the channel will be linked with a file
> * later on when debugfs is registered.
> */
and comment here as well.
> - guc_log_relay_chan = relay_open(NULL, NULL, subbuf_size,
> - n_subbufs, &relay_callbacks, dev_priv);
> + guc_log_relay_chan = relay_open("guc_log",
> + dev_priv->drm.primary->debugfs_root,
> + subbuf_size, n_subbufs,
> + &relay_callbacks, dev_priv);
> if (!guc_log_relay_chan) {
> DRM_ERROR("Couldn't create relay chan for GuC logging\n");
>
> @@ -648,18 +612,12 @@ int intel_guc_log_register(struct intel_guc *guc)
> if (ret)
> goto err_relay;
>
> - ret = guc_log_relay_file_create(guc);
> - if (ret)
> - goto err_unmap;
> -
> guc_log_flush_irq_enable(guc);
>
> mutex_unlock(&guc->log.runtime.lock);
>
> return 0;
>
> -err_unmap:
> - guc_log_unmap(guc);
> err_relay:
> guc_log_relay_destroy(guc);
> err:
--
Thanks,
Sagar
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2018-03-05 11:44 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 12:52 [PATCH 01/15] drm/i915/guc: Tidy guc_log_control Michał Winiarski
2018-02-27 12:52 ` [PATCH 02/15] drm/i915/guc: Create common entry points for log register/unregister Michał Winiarski
2018-02-27 14:11 ` Michal Wajdeczko
2018-03-05 7:09 ` Sagar Arun Kamble
2018-03-05 13:38 ` Michał Winiarski
2018-03-06 5:24 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 03/15] drm/i915/guc: Move GuC notification handling to separate function Michał Winiarski
2018-03-05 7:40 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 04/15] drm/i915/guc: Keep GuC interrupts enabled when using GuC Michał Winiarski
2018-03-05 9:27 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 05/15] drm/i915/guc: Log runtime should consist of both mapping and relay Michał Winiarski
2018-02-27 14:21 ` Michal Wajdeczko
2018-03-05 10:31 ` Sagar Arun Kamble
2018-03-05 14:14 ` Michał Winiarski
2018-03-06 5:54 ` Sagar Arun Kamble
2018-03-06 13:50 ` Chris Wilson
2018-02-27 12:52 ` [PATCH 06/15] drm/i915/guc: Merge log relay file and channel creation Michał Winiarski
2018-03-05 11:44 ` Sagar Arun Kamble [this message]
2018-02-27 12:52 ` [PATCH 07/15] drm/i915/guc: Flush directly in log unregister Michał Winiarski
2018-03-05 11:58 ` Sagar Arun Kamble
2018-03-05 12:10 ` Michał Winiarski
2018-03-06 4:59 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 08/15] drm/i915/guc: Split relay control and GuC log level Michał Winiarski
2018-03-06 7:16 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 09/15] drm/i915/guc: Move check for fast memcpy_wc to relay creation Michał Winiarski
2018-02-27 14:37 ` Michal Wajdeczko
2018-02-27 15:37 ` Michał Winiarski
2018-03-06 14:00 ` Chris Wilson
2018-03-06 7:23 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 10/15] drm/i915/guc: Get rid of GuC log runtime Michał Winiarski
2018-03-06 9:30 ` Sagar Arun Kamble
2018-03-06 14:02 ` Chris Wilson
2018-02-27 12:52 ` [PATCH 11/15] drm/i915/guc: Always print log stats in i915_guc_info when using GuC Michał Winiarski
2018-03-06 7:41 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 12/15] drm/i915/guc: Don't print out relay statistics when relay is disabled Michał Winiarski
2018-03-06 11:21 ` Sagar Arun Kamble
2018-03-06 12:00 ` Michał Winiarski
2018-03-06 13:16 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 13/15] drm/i915/guc: Allow user to control default GuC logging Michał Winiarski
2018-03-06 11:58 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 14/15] drm/i915/guc: Default to non-verbose " Michał Winiarski
2018-03-06 13:44 ` Sagar Arun Kamble
2018-02-27 12:52 ` [PATCH 15/15] HAX enable guc and guc_log for CI Michał Winiarski
2018-02-27 13:38 ` ✗ Fi.CI.SPARSE: warning for series starting with [01/15] drm/i915/guc: Tidy guc_log_control Patchwork
2018-02-27 13:47 ` ✓ Fi.CI.BAT: success " Patchwork
2018-02-27 13:49 ` [PATCH 01/15] " Michal Wajdeczko
2018-02-27 20:10 ` ✗ Fi.CI.IGT: failure for series starting with [01/15] " Patchwork
2018-03-02 11:09 ` [PATCH 01/15] " Sagar Arun Kamble
2018-03-02 11:52 ` Michał Winiarski
2018-03-05 5:29 ` Sagar Arun Kamble
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=f4f46576-c568-60c5-01b0-eedd74df771b@intel.com \
--to=sagar.a.kamble@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=michal.winiarski@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox