All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dave Olson <olson@cumulusnetworks.com>
To: Michael Ellerman <mpe@ellerman.id.au>
Cc: Paul Mackerras <paulus@samba.org>, linuxppc-dev@lists.ozlabs.org
Subject: Re: [PATCH 1/1] powerpc: fix missing L2 cache size in /sys/devices/system/cpu
Date: Mon, 9 Feb 2015 15:43:51 -0800	[thread overview]
Message-ID: <20150209234351.GC22286@cumulusnetworks.com> (raw)
In-Reply-To: <1423524827.19657.1.camel@ellerman.id.au>

Michael Ellerman <mpe@ellerman.id.au> wrote:

> On Mon, 2015-02-09 at 14:14 -0800, Dave Olson wrote:
> > From: Dave Olson <olson@cumulusnetworks.com>
> > 
> > Fix missing L2 cache size in /sys/devices/system/cpu/cpu0/cache/index2/size
> > This bug appears to be introduced in 2.6.29 by 93197a36a9c16a85fb24cf5a8639f7bf9af838a3.
> > The missing entry caused lscpu to error out on e500v2 devices, and probably others
> >  error: cannot open /sys/devices/system/cpu/cpu0/cache/index2/size: No such file or directory
> > The DTS files we see use cache-size for the unified L2 cache size, not d-cache-size
> 
> Can you convince me that this is not going to break other machines that have
> "d-cache-size" but not "cache-size"?

I'm unable to find any dts file that uses d-cache-size for the L2
unified cache.  All in the powerpc tree in arch/powerpc/boot/dts/*
are using cache-size in the L2 description for the cache size.

As best as I can tell from looking around, this is universal.

Dave Olson
olson@cumulusnetworks.com

  reply	other threads:[~2015-02-09 23:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-09 22:14 [PATCH 1/1] powerpc: fix missing L2 cache size in /sys/devices/system/cpu Dave Olson
2015-02-09 23:33 ` Michael Ellerman
2015-02-09 23:43   ` Dave Olson [this message]
2015-02-10  0:12     ` Benjamin Herrenschmidt
2015-02-10  3:30       ` Michael Ellerman
2015-02-10  8:00       ` Dave Olson
2015-02-10  8:14         ` Benjamin Herrenschmidt
2015-02-10 16:55           ` Dave Olson
2015-02-10 19:45             ` Benjamin Herrenschmidt

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=20150209234351.GC22286@cumulusnetworks.com \
    --to=olson@cumulusnetworks.com \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=mpe@ellerman.id.au \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.