From: kajoljain <kjain@linux.ibm.com>
To: Arnaldo Carvalho de Melo <acme@kernel.org>,
Peter Zijlstra <peterz@infradead.org>
Cc: jolsa@redhat.com, linux-kernel@vger.kernel.org,
linux-perf-users@vger.kernel.org, maddy@linux.ibm.com,
mingo@redhat.com, mark.rutland@arm.com,
alexander.shishkin@linux.intel.com, namhyung@kernel.org,
daniel@iogearbox.net, brho@google.com, srikar@linux.vnet.ibm.com
Subject: Re: [RFC] perf/core: Fixes hung issue on perf stat command during cpu hotplug
Date: Wed, 26 Aug 2020 20:07:20 +0530 [thread overview]
Message-ID: <135a1238-9a43-8335-e8a6-961678e95f65@linux.ibm.com> (raw)
In-Reply-To: <20200826132107.GH1059382@kernel.org>
On 8/26/20 6:51 PM, Arnaldo Carvalho de Melo wrote:
> Em Wed, Aug 26, 2020 at 03:02:36PM +0530, Kajol Jain escreveu:
>> Commit 2ed6edd33a21 ("perf: Add cond_resched() to task_function_call()")
>> added assignment of ret value as -EAGAIN in case function
>> call to 'smp_call_function_single' fails.
>> For non-zero ret value, it did
>> 'ret = !ret ? data.ret : -EAGAIN;', which always
>> assign -EAGAIN to ret and make second if condition useless.
>>
>> In scenarios like when executing a perf stat with --per-thread option, and
>> if any of the monitoring cpu goes offline, the 'smp_call_function_single'
>> function could return -ENXIO, and with the above check,
>> task_function_call hung and increases CPU
>> usage (because of repeated 'smp_call_function_single()')
>>
>> Recration scenario:
>> # perf stat -a --per-thread && (offline a CPU )
>
> Peter, this is kernel stuff, can you take a look?
>
> - Arnaldo
>
>> Patch here removes the tertiary condition added as part of that
>> commit and added a check for NULL and -EAGAIN.
>>
>> Fixes: 2ed6edd33a21("perf: Add cond_resched() to task_function_call()")
>> Signed-off-by: Kajol Jain <kjain@linux.ibm.com>
>> Reported-by: Srikar Dronamraju <srikar@linux.vnet.ibm.com>
>> ---
>> kernel/events/core.c | 6 +++---
>> 1 file changed, 3 insertions(+), 3 deletions(-)
>>
>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>> index 5bfe8e3c6e44..330c53f7df9c 100644
>> --- a/kernel/events/core.c
>> +++ b/kernel/events/core.c
>> @@ -115,9 +115,9 @@ task_function_call(struct task_struct *p, remote_function_f func, void *info)
>> for (;;) {
>> ret = smp_call_function_single(task_cpu(p), remote_function,
>> &data, 1);
>> - ret = !ret ? data.ret : -EAGAIN;
>> -
>> - if (ret != -EAGAIN)
>> + if (!ret)
>> + ret = data.ret;
>> + else if (ret != -EAGAIN)
>> break;
>>
>> cond_resched();
>> --
Hi,
Sorry for the confusion, I send wrong version of the patch. We don't have else in second
condition.
The right patch changes are:
diff --git a/kernel/events/core.c b/kernel/events/core.c
index 5bfe8e3c6e44..53d960394af9 100644
--- a/kernel/events/core.c
+++ b/kernel/events/core.c
@@ -115,8 +115,8 @@ task_function_call(struct task_struct *p, remote_function_f func, void *info)
for (;;) {
ret = smp_call_function_single(task_cpu(p), remote_function,
&data, 1);
- ret = !ret ? data.ret : -EAGAIN;
-
+ if (!ret)
+ ret = data.ret;
if (ret != -EAGAIN)
break;
I will again send the patch, please ignore this one.
Thanks,
Kajol Jain
>> 2.26.2
>>
>
next prev parent reply other threads:[~2020-08-26 14:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 9:32 [RFC] perf/core: Fixes hung issue on perf stat command during cpu hotplug Kajol Jain
2020-08-26 13:21 ` Arnaldo Carvalho de Melo
2020-08-26 14:37 ` kajoljain [this message]
2020-08-27 8:37 ` [perf/core] 16fb162e78: WARNING:at_kernel/events/core.c:#list_add_event kernel test robot
2020-08-27 13:02 ` kajoljain
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=135a1238-9a43-8335-e8a6-961678e95f65@linux.ibm.com \
--to=kjain@linux.ibm.com \
--cc=acme@kernel.org \
--cc=alexander.shishkin@linux.intel.com \
--cc=brho@google.com \
--cc=daniel@iogearbox.net \
--cc=jolsa@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=maddy@linux.ibm.com \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--cc=peterz@infradead.org \
--cc=srikar@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).