From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: mingo@redhat.com, acme@kernel.org, namhyung@kernel.org,
mark.rutland@arm.com, alexander.shishkin@linux.intel.com,
jolsa@kernel.org, irogers@google.com, adrian.hunter@intel.com,
kan.liang@linux.intel.com, linux-perf-users@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] events/core: fix acoount failure for event's total_enable_time
Date: Fri, 20 Dec 2024 15:45:33 +0000 [thread overview]
Message-ID: <Z2WRHS4CbbjTIHkQ@e129823.arm.com> (raw)
In-Reply-To: <20241220153040.GP11133@noisy.programming.kicks-ass.net>
> > It works. but what about this?
> >
> > diff --git a/kernel/events/core.c b/kernel/events/core.c
> > index 065f9188b44a..71ed8f847b04 100644
> > --- a/kernel/events/core.c
> > +++ b/kernel/events/core.c
> > @@ -2432,6 +2432,7 @@ __perf_remove_from_context(struct perf_event *event,
> > if (flags & DETACH_DEAD)
> > event->pending_disable = 1;
> > event_sched_out(event, ctx);
> > + perf_event_update_time(event);
> > if (flags & DETACH_GROUP)
> > perf_group_detach(event);
> > if (flags & DETACH_CHILD)
>
> Well, the rule is that timekeeping is tied to state change. And as you
> can see __perf_remove_from_context() violates that.
>
> Probably because someone (probably me) figured that the event would not
> be observed again after detach or something like that.
>
Ah. Thanks to let me know to think this rule.
I agree with your last suggestion.
Could I send patch with it again?
Thanks
next prev parent reply other threads:[~2024-12-20 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-20 10:02 [PATCH v2] events/core: fix acoount failure for event's total_enable_time Yeoreum Yun
2024-12-20 13:33 ` Peter Zijlstra
2024-12-20 14:05 ` Yeoreum Yun
2024-12-20 15:14 ` Peter Zijlstra
2024-12-20 15:26 ` Yeoreum Yun
2024-12-20 15:30 ` Peter Zijlstra
2024-12-20 15:45 ` Yeoreum Yun [this message]
2024-12-20 16:23 ` Yeoreum Yun
2025-01-10 16:36 ` Peter Zijlstra
2025-01-28 18:57 ` Yeo Reum Yun
2025-02-25 20:36 ` Ingo Molnar
2025-03-06 13:43 ` Yeoreum Yun
2024-12-20 15:28 ` Peter Zijlstra
2024-12-20 15:43 ` Yeoreum Yun
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=Z2WRHS4CbbjTIHkQ@e129823.arm.com \
--to=yeoreum.yun@arm.com \
--cc=acme@kernel.org \
--cc=adrian.hunter@intel.com \
--cc=alexander.shishkin@linux.intel.com \
--cc=irogers@google.com \
--cc=jolsa@kernel.org \
--cc=kan.liang@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-perf-users@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mingo@redhat.com \
--cc=namhyung@kernel.org \
--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