From: Sibi Sankar <sibis@codeaurora.org>
To: Rishabh Bhatnagar <rishabhb@codeaurora.org>
Cc: linux-remoteproc@vger.kernel.org, linux-kernel@vger.kernel.org,
bjorn.andersson@linaro.org, mathieu.poirier@linaro.org,
tsoni@codeaurora.org, psodagud@codeaurora.org,
sidgup@codeaurora.org, linux-kernel-owner@vger.kernel.org
Subject: Re: [PATCH v6 3/3] remoteproc: Add coredump debugfs entry
Date: Thu, 02 Jul 2020 01:52:51 +0530 [thread overview]
Message-ID: <483d227972b66a86b08d1abd8c396d0a@codeaurora.org> (raw)
In-Reply-To: <1593460933-4262-4-git-send-email-rishabhb@codeaurora.org>
On 2020-06-30 01:32, Rishabh Bhatnagar wrote:
> Add coredump debugfs entry to configure the type of dump that will
> be collected during recovery. User can select between default or
> inline coredump functionality. Also coredump collection can be
> disabled through this interface.
> This functionality can be configured differently for different
> remote processors.
>
> Signed-off-by: Rishabh Bhatnagar <rishabhb@codeaurora.org>
> Reviewed-by: Bjorn Andersson <bjorn.andersson@linaro.org>
> Reviewed-by: Mathieu Poirier <mathieu.poirier@linaro.org>
> ---
> drivers/remoteproc/remoteproc_debugfs.c | 86
> +++++++++++++++++++++++++++++++++
> 1 file changed, 86 insertions(+)
>
> diff --git a/drivers/remoteproc/remoteproc_debugfs.c
> b/drivers/remoteproc/remoteproc_debugfs.c
> index 732770e..cca0a91 100644
> --- a/drivers/remoteproc/remoteproc_debugfs.c
> +++ b/drivers/remoteproc/remoteproc_debugfs.c
> @@ -28,6 +28,90 @@
> static struct dentry *rproc_dbg;
>
> /*
> + * A coredump-configuration-to-string lookup table, for exposing a
> + * human readable configuration via debugfs. Always keep in sync with
> + * enum rproc_coredump_mechanism
> + */
> +static const char * const rproc_coredump_str[] = {
> + [RPROC_COREDUMP_DEFAULT] = "default",
> + [RPROC_COREDUMP_INLINE] = "inline",
> + [RPROC_COREDUMP_DISABLED] = "disabled",
> +};
> +
> +/* Expose the current coredump configuration via debugfs */
> +static ssize_t rproc_coredump_read(struct file *filp, char __user
> *userbuf,
> + size_t count, loff_t *ppos)
> +{
> + struct rproc *rproc = filp->private_data;
> + const char *buf = rproc_coredump_str[rproc->dump_conf];
Nit: It would be nice to have a
line feed after the string.
Tested-by: Sibi Sankar <sibis@codeaurora.org>
Reviewed-by: Sibi Sankar <sibis@codeaurora.org>
> +
> + return simple_read_from_buffer(userbuf, count, ppos, buf,
> strlen(buf));
> +}
> +
> +/*
> + * By writing to the 'coredump' debugfs entry, we control the behavior
> of the
> + * coredump mechanism dynamically. The default value of this entry is
> "default".
> + *
> + * The 'coredump' debugfs entry supports these commands:
> + *
> + * default: This is the default coredump mechanism. When the
> remoteproc
> + * crashes the entire coredump will be copied to a separate buffer
> + * and exposed to userspace.
> + *
> + * inline: The coredump will not be copied to a separate buffer and
> the
> + * recovery process will have to wait until data is read by
> + * userspace. But this avoid usage of extra memory.
> + *
> + * disabled: This will disable coredump. Recovery will proceed without
> + * collecting any dump.
> + */
> +static ssize_t rproc_coredump_write(struct file *filp,
> + const char __user *user_buf, size_t count,
> + loff_t *ppos)
> +{
> + struct rproc *rproc = filp->private_data;
> + int ret, err = 0;
> + char buf[20];
> +
> + if (count > sizeof(buf))
> + return -EINVAL;
> +
> + ret = copy_from_user(buf, user_buf, count);
> + if (ret)
> + return -EFAULT;
> +
> + /* remove end of line */
> + if (buf[count - 1] == '\n')
> + buf[count - 1] = '\0';
> +
> + if (rproc->state == RPROC_CRASHED) {
> + dev_err(&rproc->dev, "can't change coredump configuration\n");
> + err = -EBUSY;
> + goto out;
> + }
> +
> + if (!strncmp(buf, "disable", count)) {
> + rproc->dump_conf = RPROC_COREDUMP_DISABLED;
> + } else if (!strncmp(buf, "inline", count)) {
> + rproc->dump_conf = RPROC_COREDUMP_INLINE;
> + } else if (!strncmp(buf, "default", count)) {
> + rproc->dump_conf = RPROC_COREDUMP_DEFAULT;
> + } else {
> + dev_err(&rproc->dev, "Invalid coredump configuration\n");
> + err = -EINVAL;
> + }
> +out:
> + return err ? err : count;
> +}
> +
> +static const struct file_operations rproc_coredump_fops = {
> + .read = rproc_coredump_read,
> + .write = rproc_coredump_write,
> + .open = simple_open,
> + .llseek = generic_file_llseek,
> +};
> +
> +/*
> * Some remote processors may support dumping trace logs into a shared
> * memory buffer. We expose this trace buffer using debugfs, so users
> * can easily tell what's going on remotely.
> @@ -337,6 +421,8 @@ void rproc_create_debug_dir(struct rproc *rproc)
> rproc, &rproc_rsc_table_fops);
> debugfs_create_file("carveout_memories", 0400, rproc->dbg_dir,
> rproc, &rproc_carveouts_fops);
> + debugfs_create_file("coredump", 0600, rproc->dbg_dir,
> + rproc, &rproc_coredump_fops);
> }
>
> void __init rproc_init_debugfs(void)
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project.
prev parent reply other threads:[~2020-07-01 20:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 20:02 [PATCH v6 0/3] Extend coredump functionality Rishabh Bhatnagar
2020-06-29 20:02 ` [PATCH v6 1/3] remoteproc: Move coredump functionality to a new file Rishabh Bhatnagar
2020-07-01 20:10 ` Sibi Sankar
2020-06-29 20:02 ` [PATCH v6 2/3] remoteproc: Add inline coredump functionality Rishabh Bhatnagar
2020-07-01 20:20 ` Sibi Sankar
2020-07-06 17:47 ` Mathieu Poirier
2020-07-07 17:12 ` rishabhb
2020-07-07 21:55 ` Mathieu Poirier
2020-06-29 20:02 ` [PATCH v6 3/3] remoteproc: Add coredump debugfs entry Rishabh Bhatnagar
2020-07-01 20:22 ` Sibi Sankar [this message]
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=483d227972b66a86b08d1abd8c396d0a@codeaurora.org \
--to=sibis@codeaurora.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-kernel-owner@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=psodagud@codeaurora.org \
--cc=rishabhb@codeaurora.org \
--cc=sidgup@codeaurora.org \
--cc=tsoni@codeaurora.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