From: Song Liu <songliubraving@fb.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
Arnaldo Carvalho de Melo <acme@kernel.org>,
Ingo Molnar <mingo@redhat.com>, Kernel Team <Kernel-team@fb.com>,
Stephane Eranian <eranian@google.com>,
Lucian Grijincu <lucian@fb.com>
Subject: Re: [PATCH v2] perf/core: fix userpage->time_enabled of inactive events
Date: Wed, 29 Sep 2021 19:38:12 +0000 [thread overview]
Message-ID: <59D2F040-D16F-4ECE-9977-C5187127FB84@fb.com> (raw)
In-Reply-To: <YVQvYUuokUnev0tG@hirez.programming.kicks-ass.net>
> On Sep 29, 2021, at 2:18 AM, Peter Zijlstra <peterz@infradead.org> wrote:
>
> On Thu, Sep 23, 2021 at 06:28:00PM -0700, Song Liu wrote:
>
>> diff --git a/kernel/events/core.c b/kernel/events/core.c
>> index 1cb1f9b8392e2..d73f986eef7b3 100644
>> --- a/kernel/events/core.c
>> +++ b/kernel/events/core.c
>> @@ -3707,6 +3707,46 @@ static noinline int visit_groups_merge(struct perf_cpu_context *cpuctx,
>> return 0;
>> }
>>
>> +static inline bool event_update_userpage(struct perf_event *event)
>> +{
>> + /*
>> + * Checking mmap_count to avoid unnecessary work. This does leave a
>> + * corner case: if the event is enabled before mmap(), the first
>> + * time the event gets scheduled is via:
>> + *
>> + * __perf_event_enable (or __perf_install_in_context)
>> + * -> ctx_resched
>> + * -> perf_event_sched_in
>> + * -> ctx_sched_in
>> + *
>> + * with mmap_count of 0, so we will skip here. As a result,
>> + * userpage->offset is not accurate after mmap and before the
>> + * first rotation.
>> + *
>> + * To avoid the discrepancy of this window, the user space should
>> + * mmap the event before enabling it.
>> + */
>
> It seems to me that writing that comment was more work than actually
> fixing perf_mmap() to DTRT, no? AFAICT all we need is something like:
>
> diff --git a/kernel/events/core.c b/kernel/events/core.c
> index fd2ae70fa6c4..1e33c2e6b0dc 100644
> --- a/kernel/events/core.c
> +++ b/kernel/events/core.c
> @@ -6324,6 +6324,8 @@ static int perf_mmap(struct file *file, struct vm_area_struct *vma)
>
> ring_buffer_attach(event, rb);
>
> + perf_event_update_time(event);
> + perf_set_shadow_time(event, event->ctx);
> perf_event_init_userpage(event);
> perf_event_update_userpage(event);
> } else {
Yeah, this does work. I will fold this in v3.
Thanks,
Song
next prev parent reply other threads:[~2021-09-29 19:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-24 1:28 Song Liu
2021-09-27 16:33 ` Song Liu
2021-09-29 9:18 ` Peter Zijlstra
2021-09-29 19:38 ` Song Liu [this message]
2021-09-29 17:04 ` Athira Rajeev
2021-09-29 19:41 ` Song Liu
2021-09-30 4:32 ` Athira Rajeev
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=59D2F040-D16F-4ECE-9977-C5187127FB84@fb.com \
--to=songliubraving@fb.com \
--cc=Kernel-team@fb.com \
--cc=acme@kernel.org \
--cc=eranian@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lucian@fb.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.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®