From: Chris Wilson <chris@chris-wilson.co.uk>
To: akash.goel@intel.com
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org,
viro@zeniv.linux.org.uk,
Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>,
Tom Zanussi <tzanussi@gmail.com>
Subject: Re: [PATCH] relay: Add global mode support for buffer-only channels
Date: Mon, 4 Jul 2016 09:00:38 +0100 [thread overview]
Message-ID: <20160704080038.GA25596@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1467562527-21569-1-git-send-email-akash.goel@intel.com>
On Sun, Jul 03, 2016 at 09:45:27PM +0530, akash.goel@intel.com wrote:
> From: Akash Goel <akash.goel@intel.com>
>
> The following patch added support to use channels with no associated files.
> relay: add buffer-only channels; useful for early logging
> This is useful when the exact location of relay file is not known or the
> the parent directory of relay file is not available, while creating the
> channel and the logging has to start right from the boot.
>
> But there was no provision to use global mode with buffer-only channels,
> which is added by this patch, without modifying the interface where initially
> there will be a dummy invocation of create_buf_file callback through which
> kernel client can convey the need of a global buffer.
>
> For the use case where drivers/kernel clients want a simple interface for the
> userspace, which enables them to capture data/logs from relay file in order &
> without any post processing, support of Global buffer mode is warranted.
>
> Cc: Eduard - Gabriel Munteanu <eduard.munteanu@linux360.ro>
> Cc: Tom Zanussi <tzanussi@gmail.com>
> Cc: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Akash Goel <akash.goel@intel.com>
> ---
> kernel/relay.c | 32 ++++++++++++++++++++++++++++++++
> 1 file changed, 32 insertions(+)
>
> diff --git a/kernel/relay.c b/kernel/relay.c
> index 04d7cf3..b267384 100644
> --- a/kernel/relay.c
> +++ b/kernel/relay.c
> @@ -451,6 +451,16 @@ static struct rchan_buf *relay_open_buf(struct rchan *chan, unsigned int cpu)
> if (!dentry)
> goto free_buf;
> relay_set_buf_dentry(buf, dentry);
> + } else {
The trailing block can be replaced with:
/* Only retrieve global info, nothing more, nothing less */
> + dentry = chan->cb->create_buf_file(NULL, NULL,
> + S_IRUSR, buf,
> + &chan->is_global);
Watch alignment, align to the opening bracket.
> + if (WARN_ON(dentry))
> + goto free_buf;
> }
>
> buf->cpu = cpu;
> @@ -666,6 +676,27 @@ int relay_late_setup_files(struct rchan *chan,
> }
> chan->has_base_filename = 1;
> chan->parent = parent;
> +
> + if (chan->is_global) {
> + if (unlikely(!chan->buf[0])) {
if (WARN_ON_ONCE(!chan->buf[0])) {
> + WARN_ONCE(1, KERN_ERR "CPU 0 has no buffer!\n");
The WARN includes the unlikely and the message here isn't any more
informative than the line itself, plus has the erroneous KERN_ERR
> + mutex_unlock(&relay_channels_mutex);
> + return -EINVAL;
> + }
> +
> + dentry = relay_create_buf_file(chan, chan->buf[0], 0);
> +
> + if (unlikely(!dentry))
> + err = -EINVAL;
> + else if (WARN_ON(!chan->is_global))
?
> + err = -EINVAL;
> + else
> + relay_set_buf_dentry(chan->buf[0], dentry);
> +
> + mutex_unlock(&relay_channels_mutex);
> + return err;
This could be written:
if (chan->is_global) {
err = -EINVAL;
if (!WARN_ON_ONCE(!chan->buf[0])) {
dentry = relay_create_buf_file(chan, chan->buf[0], 0))
if (dentry) {
relay_set_buf_dentry(chan->buf[0], dentry);
err = 0;
}
}
mutex_unlock();
return err;
}
for a single exit/unlock path in this block.
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2016-07-04 8:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-03 16:15 akash.goel
2016-07-04 8:00 ` Chris Wilson [this message]
2016-07-04 13:03 ` Goel, Akash
2016-07-11 7:17 ` [PATCH v2] " akash.goel
2016-07-11 20:17 ` Andrew Morton
2016-07-12 9:24 ` Chris Wilson
2016-07-12 12:50 ` Goel, Akash
2016-07-12 13:01 ` Chris Wilson
2016-07-12 13:24 ` Goel, Akash
2016-07-12 19:51 ` Andrew Morton
2016-07-13 7:39 ` [PATCH v3] " akash.goel
2016-07-13 8:30 ` kbuild test robot
2016-07-13 10:09 ` [PATCH v4] " 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=20160704080038.GA25596@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=akash.goel@intel.com \
--cc=akpm@linux-foundation.org \
--cc=eduard.munteanu@linux360.ro \
--cc=linux-kernel@vger.kernel.org \
--cc=tzanussi@gmail.com \
--cc=viro@zeniv.linux.org.uk \
/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
all inboxes | Powered by JetHome®