linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: dave.martin@linaro.org (Dave Martin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: Allow modules to read cpu_logical_map
Date: Fri, 8 Feb 2013 14:32:03 +0000	[thread overview]
Message-ID: <20130208143203.GB1973@linaro.org> (raw)
In-Reply-To: <20130208122604.GO17833@n2100.arm.linux.org.uk>

On Fri, Feb 08, 2013 at 12:26:04PM +0000, Russell King - ARM Linux wrote:
> On Fri, Feb 08, 2013 at 12:19:40PM +0000, Dave Martin wrote:
> > It is reasonable for loadable modules to be CPU topology aware
> > (particular examples include cpufreq and cpuidle drivers).
> > 
> > This patch exports a new function cpu_get_hwid(cpu) to provide
> > suitable read-only access outside vmlinux.
> 
> And we have an export with no user... where are the patches which
> illustrate its usage?

That's a fair point.

The background is that ARM have an out-of-tree profiling driver,
which may need to look at cpu_logical_map in the presence of the
big.LITTLE in-kernel switcher code.

Although there is no in-tree code using this yet, the usage seems
legitimate.

If there are outstanding concerns about this, this patch could stay
out-of-tree too, but said driver would only work with a modified
kernel in that case.

If this is not considered relevant to the kernel proper yet, then
it could be posted via the big.LITTLE in-kernel switcher series
when those are finally published, since it is this that causes
cpu_logical_map to change in ways that a few specialised drivers
may need to respond to.  Without the switcher, no code should need
to look at cpu_logical_map (the present situation).

(Nico, please shout if you have any concerns about that approach.)

Cheers
---Dave

      reply	other threads:[~2013-02-08 14:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-08 12:19 [PATCH] ARM: Allow modules to read cpu_logical_map Dave Martin
2013-02-08 12:26 ` Russell King - ARM Linux
2013-02-08 14:32   ` Dave Martin [this message]

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=20130208143203.GB1973@linaro.org \
    --to=dave.martin@linaro.org \
    --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).