linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sudeep Holla <sudeep.holla@arm.com>
To: Heiko Carstens <heiko.carstens@de.ibm.com>,
	Stephen Boyd <sboyd@codeaurora.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: Sudeep Holla <sudeep.holla@arm.com>,
	"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [-next] cpu cache info in drivers base?
Date: Mon, 24 Nov 2014 16:06:19 +0000	[thread overview]
Message-ID: <5473577B.6010708@arm.com> (raw)
In-Reply-To: <20141124150048.GD3738@osiris>

Hi Heiko,

On 24/11/14 15:00, Heiko Carstens wrote:
> 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".

That's correct, I did post a patch[1] to suppress that given not all
architectures might add support.

> 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?

Yes, I asked Greg to hold off on the architecture patches for next
versions as there may be conflicts(though we can have solve it using
a common baseline, but I thought it was too late to try that). Also
I have not got testing on few other architectures(ppc, ia64, amd). I
will post those patches individually on respective arch lists and
chase after the v3.19-rc1 release. Is that OK ?

Regards,
Sudeep

[1] https://lkml.org/lkml/2014/11/12/351

  reply	other threads:[~2014-11-24 16:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-24 15:00 [-next] cpu cache info in drivers base? Heiko Carstens
2014-11-24 16:06 ` Sudeep Holla [this message]
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=5473577B.6010708@arm.com \
    --to=sudeep.holla@arm.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=heiko.carstens@de.ibm.com \
    --cc=linux-next@vger.kernel.org \
    --cc=sboyd@codeaurora.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).