From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-next@vger.kernel.org
Subject: [-next] cpu cache info in drivers base?
Date: Mon, 24 Nov 2014 16:00:48 +0100 [thread overview]
Message-ID: <20141124150048.GD3738@osiris> (raw)
Hi there,
I'm just wondering what the point of the current cpu cache info
within drivers/base is?
If I startup linux-next (as of today) all I get is an error message
"error detecting cacheinfo..cpu0".
Which naturally comes from:
int __weak init_cache_level(unsigned int cpu)
{
return -ENOENT;
}
Given that there is no implementation without __weak I'm wondering
what the point is? Also it looks like no architecture has been
converted to the new infrastructure, even though such patches have
been posted in the past?
next reply other threads:[~2014-11-24 15:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-24 15:00 Heiko Carstens [this message]
2014-11-24 16:06 ` [-next] cpu cache info in drivers base? Sudeep Holla
2014-11-24 17:33 ` Greg Kroah-Hartman
2014-11-25 6:44 ` Heiko Carstens
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=20141124150048.GD3738@osiris \
--to=heiko.carstens@de.ibm.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-next@vger.kernel.org \
--cc=sboyd@codeaurora.org \
--cc=sudeep.holla@arm.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 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).