From: Waiman Long <longman@redhat.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Bharata B Rao <bharata@linux.vnet.ibm.com>,
Phil Auld <pauld@redhat.com>,
Daniel Thompson <daniel.thompson@linaro.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4] sched/debug: Use sched_debug_lock to serialize use of cgroup_path[] only
Date: Mon, 5 Apr 2021 21:57:07 -0400 [thread overview]
Message-ID: <5c4d0d47-5503-76a2-0f27-1b4b13c34aa5@redhat.com> (raw)
In-Reply-To: <20210405201807.4ee7778d@gandalf.local.home>
On 4/5/21 8:18 PM, Steven Rostedt wrote:
> On Mon, 5 Apr 2021 19:42:03 -0400
> Waiman Long <longman@redhat.com> wrote:
>
>> +/*
>> + * All the print_cpu() callers from sched_debug_show() will be allowed
>> + * to contend for sched_debug_lock and use group_path[] as their SEQ_printf()
>> + * calls will be much faster. However only one print_cpu() caller from
>> + * sysrq_sched_debug_show() which outputs to the console will be allowed
>> + * to use group_path[]. Another parallel console writer will have to use
>> + * a shorter stack buffer instead. Since the console output will be garbled
>> + * anyway, truncation of some cgroup paths shouldn't be a big issue.
>> + */
>> +#define SEQ_printf_task_group_path(m, tg, fmt...) \
>> +{ \
>> + unsigned long flags; \
>> + int token = m ? TOKEN_NA \
>> + : xchg_acquire(&console_token, TOKEN_NONE); \
>> + \
>> + if (token == TOKEN_NONE) { \
>> + char buf[128]; \
>> + task_group_path(tg, buf, sizeof(buf)); \
>> + SEQ_printf(m, fmt, buf); \
>> + } else { \
>> + spin_lock_irqsave(&sched_debug_lock, flags); \
>> + task_group_path(tg, group_path, sizeof(group_path)); \
>> + SEQ_printf(m, fmt, group_path); \
>> + spin_unlock_irqrestore(&sched_debug_lock, flags); \
>> + if (token == TOKEN_ACQUIRED) \
>> + smp_store_release(&console_token, token); \
>> + } \
>> }
>> #endif
> And you said my suggestion was complex!
>
> I'll let others review this.
>
This patch is actually inspired by your suggestion, though it is
structured differently from your approach. I really want to thank you
for your valuable feedback.
I realized that printing to a sequence file wasn't really a problem,
only printing to console can be problematic. That is why I decided to
allow unlimited use of group_path[] for those users and only one console
writer is allowed to use it. As for calling touch_nmi_watchdog(), I am
still thinking where will be the right place to do it, but it can be
done with a separate patch, if needed.
Cheers,
Longman
next prev parent reply other threads:[~2021-04-06 1:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-05 23:42 Waiman Long
2021-04-06 0:18 ` Steven Rostedt
2021-04-06 1:57 ` Waiman Long [this message]
2021-04-06 9:15 ` Peter Zijlstra
2021-04-06 15:17 ` Waiman Long
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=5c4d0d47-5503-76a2-0f27-1b4b13c34aa5@redhat.com \
--to=longman@redhat.com \
--cc=bharata@linux.vnet.ibm.com \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=daniel.thompson@linaro.org \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=pauld@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.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
all inboxes | Powered by JetHome®