From: Vincent Donnefort <vincent.donnefort@arm.com>
To: peterz@infradead.org
Cc: mingo@redhat.com, vincent.guittot@linaro.org,
linux-kernel@vger.kernel.org, dietmar.eggemann@arm.com,
lukasz.luba@arm.com, valentin.schneider@arm.com
Subject: Re: [PATCH] sched/fair: provide u64 read for 32-bits arch helper
Date: Tue, 18 Aug 2020 19:11:20 +0100 [thread overview]
Message-ID: <20200818181120.GA297937@e120877-lin.cambridge.arm.com> (raw)
In-Reply-To: <20200728195320.GA426859@e120877-lin.cambridge.arm.com>
Hi Peter,
[...]
> > >
> > > How about something like:
> > >
> > > #ifdef CONFIG_64BIT
> > >
> > > #define DEFINE_U64_U32(name) u64 name
> > > #define u64_u32_load(name) name
> > > #define u64_u32_store(name, val)name = val
> > >
> > > #else
> > >
> > > #define DEFINE_U64_U32(name) \
> > > struct { \
> > > u64 name; \
> > > u64 name##_copy; \
> > > }
> > >
> > > #define u64_u32_load(name) \
> > > ({ \
> > > u64 val, copy; \
> > > do { \
> > > val = name; \
> > > smb_rmb(); \
> > > copy = name##_copy; \
> > > } while (val != copy); \
> >
> > wrong order there; we should first read _copy and then the regular one
> > of course.
> >
> > > val;
> > > })
> > >
> > > #define u64_u32_store(name, val) \
> > > do { \
> > > typeof(val) __val = (val); \
> > > name = __val; \
> > > smp_wmb(); \
> > > name##_copy = __val; \
> > > } while (0)
> > >
> > > #endif
> >
> > The other approach is making it a full type and inline functions I
> > suppose.
>
> I didn't pick this approach originally, as I thought it would be way too
> invasive. If the API looks way cleaner, it nonetheless doesn't match
> last_update_time usage. The variable is declared in sched_avg while its copy
> is in struct cfs_rq.
>
> Moving the copy in sched_avg would mean:
>
> * Setting the copy for all struct sched_avg in ___update_load_sum(), instead
> of just the cfs_rq.avg in update_cfs_rq_load_avg().
>
> * Having the DEFINE_U64_U32 declaration in include/linux/sched.h to cover
> struct sched_avg.
Gentle ping
next prev parent reply other threads:[~2020-08-18 18:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-27 10:59 vincent.donnefort
2020-07-27 11:24 ` Ingo Molnar
2020-07-27 12:05 ` Vincent Donnefort
2020-07-27 12:38 ` peterz
2020-07-27 15:23 ` Vincent Donnefort
2020-07-28 11:13 ` peterz
2020-07-28 12:00 ` peterz
2020-07-28 19:53 ` Vincent Donnefort
2020-08-18 18:11 ` Vincent Donnefort [this message]
2020-07-28 9:09 ` Lukasz Luba
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=20200818181120.GA297937@e120877-lin.cambridge.arm.com \
--to=vincent.donnefort@arm.com \
--cc=dietmar.eggemann@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukasz.luba@arm.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=valentin.schneider@arm.com \
--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®