From: mans@mansr.com (Måns Rullgård)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] sched_clock: add data pointer argument to read callback
Date: Sat, 10 Oct 2015 00:48:22 +0100 [thread overview]
Message-ID: <yw1x4mhzioxl.fsf@unicorn.mansr.com> (raw)
In-Reply-To: <20151009232015.GC32536@n2100.arm.linux.org.uk> (Russell King's message of "Sat, 10 Oct 2015 00:20:15 +0100")
Russell King - ARM Linux <linux@arm.linux.org.uk> writes:
> On Fri, Oct 09, 2015 at 10:57:35PM +0100, Mans Rullgard wrote:
>> This passes a data pointer specified in the sched_clock_register()
>> call to the read callback allowing simpler implementations thereof.
>>
>> In this patch, existing uses of this interface are simply updated
>> with a null pointer.
>
> This is a bad description. It tells us what the patch is doing,
> (which we can see by reading the patch) but not _why_. Please include
> information on why the change is necessary - describe what you are
> trying to achieve.
Currently most of the callbacks use a global variable to store the
address of a counter register. This has several downsides:
- Loading the address of a global variable can be more expensive than
keeping a pointer next to the function pointer.
- It makes it impossible to have multiple instances of a driver call
sched_clock_register() since the caller can't know which clock will
win in the end.
- Many of the existing callbacks are practically identical and could be
replaced with a common generic function if it had a pointer argument.
If I've missed something that makes this a stupid idea, please tell.
--
M?ns Rullg?rd
mans at mansr.com
next prev parent reply other threads:[~2015-10-09 23:48 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1444427858-576-1-git-send-email-mans@mansr.com>
2015-10-09 23:20 ` [PATCH] sched_clock: add data pointer argument to read callback Russell King - ARM Linux
2015-10-09 23:48 ` Måns Rullgård [this message]
2015-10-09 23:54 ` Russell King - ARM Linux
2015-10-10 0:42 ` Måns Rullgård
2015-10-10 15:33 ` Russell King - ARM Linux
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=yw1x4mhzioxl.fsf@unicorn.mansr.com \
--to=mans@mansr.com \
--cc=linux-arm-kernel@lists.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;
as well as URLs for NNTP newsgroup(s).