From: Changwoo Min <changwoo@igalia.com>
To: Peter Zijlstra <peterz@infradead.org>,
Changwoo Min <multics69@gmail.com>
Cc: tj@kernel.org, void@manifault.com, arighi@nvidia.com,
mingo@redhat.com, kernel-dev@igalia.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v7 2/6] sched_ext: Implement scx_bpf_now()
Date: Thu, 9 Jan 2025 01:04:49 +0900 [thread overview]
Message-ID: <c1e5bd3b-cefc-4e74-ae7f-b8ffebe8c745@igalia.com> (raw)
In-Reply-To: <20250108085026.GC23315@noisy.programming.kicks-ass.net>
Hello,
On 25. 1. 8. 17:50, Peter Zijlstra wrote:
>
> That is, I rather think you need:
>
>> +static inline void scx_rq_clock_update(struct rq *rq, u64 clock)
>> +{
>> + if (!scx_enabled())
>> + return;
>> + WRITE_ONCE(rq->scx.clock, clock);
>> + smp_store_release(&rq->scx.flags, rq->scx.flags | SCX_RQ_CLK_VALID);
>> +}
>
> and:
>
> if (smp_load_acquire(&rq->scx.flags) & SCX_RQ_CLK_VALID) {
>> + /*
>> + * If the rq clock is valid, use the cached rq clock.
>> + *
>> + * Note that scx_bpf_now() is re-entrant between a process
>> + * context and an interrupt context (e.g., timer interrupt).
>> + * However, we don't need to consider the race between them
>> + * because such race is not observable from a caller.
>> + */
>> + clock = READ_ONCE(rq->scx.clock);
>
> Such that if you ovbserve VALID, you must then also observe the clock.
Thank you for catching this out! I will change it as suggested in
the next version.
Regards,
Changwoo Min
next prev parent reply other threads:[~2025-01-08 16:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-30 9:56 [PATCH v7 0/6] sched_ext: Support high-performance monotonically non-decreasing clock Changwoo Min
2024-12-30 9:56 ` [PATCH v7 1/6] sched_ext: Relocate scx_enabled() related code Changwoo Min
2024-12-30 9:56 ` [PATCH v7 2/6] sched_ext: Implement scx_bpf_now() Changwoo Min
2025-01-08 8:50 ` Peter Zijlstra
2025-01-08 16:04 ` Changwoo Min [this message]
2024-12-30 9:56 ` [PATCH v7 3/6] sched_ext: Add scx_bpf_now() for BPF scheduler Changwoo Min
2024-12-30 9:56 ` [PATCH v7 4/6] sched_ext: Add time helpers for BPF schedulers Changwoo Min
2024-12-30 9:56 ` [PATCH v7 5/6] sched_ext: Replace bpf_ktime_get_ns() to scx_bpf_now() Changwoo Min
2024-12-30 9:56 ` [PATCH v7 6/6] sched_ext: Use time helpers in BPF schedulers Changwoo Min
2025-01-02 18:54 ` [PATCH v7 0/6] sched_ext: Support high-performance monotonically non-decreasing clock Andrea Righi
2025-01-03 22:16 ` Tejun Heo
2025-01-07 19:46 ` Tejun Heo
2025-01-07 19:53 ` Peter Zijlstra
2025-01-07 19:55 ` Tejun Heo
2025-01-08 8:51 ` Peter Zijlstra
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=c1e5bd3b-cefc-4e74-ae7f-b8ffebe8c745@igalia.com \
--to=changwoo@igalia.com \
--cc=arighi@nvidia.com \
--cc=kernel-dev@igalia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=multics69@gmail.com \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=void@manifault.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 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.