All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paolo Valente <paolo.valente@linaro.org>
To: Jan Kara <jack@suse.cz>
Cc: Jens Axboe <axboe@kernel.dk>, linux-block@vger.kernel.org
Subject: Re: [PATCH] blktrace: Report pid with note messages
Date: Thu, 14 May 2020 00:04:12 +0200	[thread overview]
Message-ID: <E45FC662-D4FB-4927-8DE3-22E22687B643@linaro.org> (raw)
In-Reply-To: <20200513160223.7855-1-jack@suse.cz>



> Il giorno 13 mag 2020, alle ore 18:02, Jan Kara <jack@suse.cz> ha scritto:
> 
> Currently informational messages within block trace do not have PID
> information of the process reporting the message included. With BFQ it
> is sometimes useful to have the information and there's no good reason
> to omit the information from the trace. So just fill in pid information
> when generating note message.
> 

Acked-by: Paolo Valente <paolo.valente@linaro.org>

Thank you!
Paolo

> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
> kernel/trace/blktrace.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/kernel/trace/blktrace.c b/kernel/trace/blktrace.c
> index ca39dc3230cb..ea47f2084087 100644
> --- a/kernel/trace/blktrace.c
> +++ b/kernel/trace/blktrace.c
> @@ -170,10 +170,10 @@ void __trace_note_message(struct blk_trace *bt, struct blkcg *blkcg,
> 	if (!(blk_tracer_flags.val & TRACE_BLK_OPT_CGROUP))
> 		blkcg = NULL;
> #ifdef CONFIG_BLK_CGROUP
> -	trace_note(bt, 0, BLK_TN_MESSAGE, buf, n,
> +	trace_note(bt, current->pid, BLK_TN_MESSAGE, buf, n,
> 		   blkcg ? cgroup_id(blkcg->css.cgroup) : 1);
> #else
> -	trace_note(bt, 0, BLK_TN_MESSAGE, buf, n, 0);
> +	trace_note(bt, current->pid, BLK_TN_MESSAGE, buf, n, 0);
> #endif
> 	local_irq_restore(flags);
> }
> -- 
> 2.16.4
> 


  reply	other threads:[~2020-05-13 22:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-13 16:02 [PATCH] blktrace: Report pid with note messages Jan Kara
2020-05-13 22:04 ` Paolo Valente [this message]
2020-05-16  4:10 ` Chaitanya Kulkarni
2020-05-16 20:30 ` Jens Axboe

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=E45FC662-D4FB-4927-8DE3-22E22687B643@linaro.org \
    --to=paolo.valente@linaro.org \
    --cc=axboe@kernel.dk \
    --cc=jack@suse.cz \
    --cc=linux-block@vger.kernel.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.