From: Dave Olson <redacted>
This problem appears to have been introduced in 2.6.29 by
93197a36a9c16a85fb24cf5a8639f7bf9af838a3.
This 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
Some embedded powerpc systems use cache-size in DTS for the unified L2 cache
size, not d-cache-size, so we need to allow for both DTS names. Added a
new CACHE_TYPE_UNIFIED_D cache_type_info structure to handle this.
This patch is against git://git.kernel.org/pub/scm/linux/kernel/git/benh/powerpc.git
next branch. It is the same as the v2 patch, but against next, rather than master.
I can rebase, if desired.
Signed-off-by: Dave Olson <redacted>
---
arch/powerpc/kernel/cacheinfo.c | 38 ++++++++++++++++++++++++++++++++++----
1 file changed, 34 insertions(+), 4 deletions(-)
@@ -61,12 +61,22 @@ struct cache_type_info {};/* These are used to index the cache_type_info array. */-#define CACHE_TYPE_UNIFIED 0-#define CACHE_TYPE_INSTRUCTION 1-#define CACHE_TYPE_DATA 2+#define CACHE_TYPE_UNIFIED 0 /* cache-size, cache-block-size, etc. */+#define CACHE_TYPE_UNIFIED_D 1 /* d-cache-size, d-cache-block-size, etc */+#define CACHE_TYPE_INSTRUCTION 2+#define CACHE_TYPE_DATA 3staticconststructcache_type_infocache_type_info[]={{+/* Embedded systems that use cache-size, cache-block-size,+*etc.fortheUnified(typicallyL2)cache.*/+.name="Unified",+.size_prop="cache-size",+.line_size_props={"cache-line-size",+"cache-block-size",},+.nr_sets_prop="cache-sets",+},+{/* PowerPC Processor binding says the [di]-cache-**mustbeequalonunifiedcaches,sojustuse*d-cacheproperties.*/
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2015-03-26 04:49:28
On Thu, 2015-26-02 at 00:04:47 UTC, Dave Olson wrote:
quoted hunk
@@ -324,14 +335,33 @@ static bool cache_node_is_unified(const struct device_node *np) return of_get_property(np, "cache-unified", NULL); }+/*+ * Handle unified caches that have two different types of tags. Most embedded+ * use cache-size, etc. for the unified cache size, but open firmware systems+ * use d-cache-size, etc. Since they all appear to be consistent, check on+ * initialization for which type we are, and use the appropriate structure.+ */ static struct cache *cache_do_one_devnode_unified(struct device_node *node, int level) { struct cache *cache;+ int ucache; pr_debug("creating L%d ucache for %s\n", level, node->full_name); cache = new_cache(CACHE_TYPE_UNIFIED, level, node);
That looks fishy. You create a cache, and then throw it away and create another
one and return that. I don't think that's what you intended, is it?
It would also be cleaner I think if you created another helper, eg.
cache_is_unified_d() to do the property lookup.
And also I don't think you need to do the second property lookup, especially if
all you're going to do is print a warning.
cheers
From: Dave Olson <hidden> Date: 2015-03-26 19:49:26
Michael Ellerman [off-list ref] wrote:
On Thu, 2015-26-02 at 00:04:47 UTC, Dave Olson wrote:
quoted
@@ -324,14 +335,33 @@ static bool cache_node_is_unified(const struct device_node *np) return of_get_property(np, "cache-unified", NULL); }+/*+ * Handle unified caches that have two different types of tags. Most embedded+ * use cache-size, etc. for the unified cache size, but open firmware systems+ * use d-cache-size, etc. Since they all appear to be consistent, check on+ * initialization for which type we are, and use the appropriate structure.+ */ static struct cache *cache_do_one_devnode_unified(struct device_node *node, int level) { struct cache *cache;+ int ucache; pr_debug("creating L%d ucache for %s\n", level, node->full_name); cache = new_cache(CACHE_TYPE_UNIFIED, level, node);
That looks fishy. You create a cache, and then throw it away and create another
one and return that. I don't think that's what you intended, is it?
It looks like I missed something when I regenerated the patch, yes.
My version of cacheinfo.c doesn't have the first new_cache() call.
It would also be cleaner I think if you created another helper, eg.
cache_is_unified_d() to do the property lookup.
OK.
And also I don't think you need to do the second property lookup, especially if
all you're going to do is print a warning.
I wanted to make sure that if a similar issue arose in the future, that
a message was printed so it got caught and fixed. I don't see a way
to do that without the 2nd lookup.
Let me know what you think, and I'll generate another patch.
Dave Olson
olson@cumulusnetworks.com
From: Michael Ellerman <mpe@ellerman.id.au> Date: 2015-03-26 23:39:57
On Thu, 2015-03-26 at 12:49 -0700, Dave Olson wrote:
Michael Ellerman [off-list ref] wrote:
quoted
On Thu, 2015-26-02 at 00:04:47 UTC, Dave Olson wrote:
quoted
@@ -324,14 +335,33 @@ static bool cache_node_is_unified(const struct device_node *np) return of_get_property(np, "cache-unified", NULL); }+/*+ * Handle unified caches that have two different types of tags. Most embedded+ * use cache-size, etc. for the unified cache size, but open firmware systems+ * use d-cache-size, etc. Since they all appear to be consistent, check on+ * initialization for which type we are, and use the appropriate structure.+ */ static struct cache *cache_do_one_devnode_unified(struct device_node *node, int level) { struct cache *cache;+ int ucache; pr_debug("creating L%d ucache for %s\n", level, node->full_name); cache = new_cache(CACHE_TYPE_UNIFIED, level, node);
That looks fishy. You create a cache, and then throw it away and create another
one and return that. I don't think that's what you intended, is it?
It looks like I missed something when I regenerated the patch, yes.
My version of cacheinfo.c doesn't have the first new_cache() call.
OK, not sure how you did that. I recommend using git to generate the patch.
quoted
And also I don't think you need to do the second property lookup, especially if
all you're going to do is print a warning.
I wanted to make sure that if a similar issue arose in the future, that
a message was printed so it got caught and fixed. I don't see a way
to do that without the 2nd lookup.
That's an admirable goal but I don't think that's the right way to catch it. If
it's important then someone needs to be testing the end result, ie. the
contents of /sys/devices/system/cpu/*/cache.
Also a single printk is never going to get noticed in the boot log, unless
someone's already looking for it.
cheers
From: Dave Olson <redacted>
This is version 4 of the patch, incorporating Michael Ellerman's
suggested changes from March 26, 2015.
================
This problem appears to have been introduced in 2.6.29 by
the commit in the Fixes line below.
This 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
Some embedded powerpc systems use cache-size in DTS for the unified L2 cache
size, not d-cache-size, so we need to allow for both DTS names. Added a
new CACHE_TYPE_UNIFIED_D cache_type_info structure to handle this.
Fixes: 93197a36a9c16a85fb24cf5a8639f7bf9af838a3
Signed-off-by: Dave Olson <redacted>
---
arch/powerpc/kernel/cacheinfo.c | 44 ++++++++++++++++++++++++++++++---------
1 file changed, 34 insertions(+), 10 deletions(-)
@@ -61,12 +61,22 @@ struct cache_type_info {};/* These are used to index the cache_type_info array. */-#define CACHE_TYPE_UNIFIED 0-#define CACHE_TYPE_INSTRUCTION 1-#define CACHE_TYPE_DATA 2+#define CACHE_TYPE_UNIFIED 0 /* cache-size, cache-block-size, etc. */+#define CACHE_TYPE_UNIFIED_D 1 /* d-cache-size, d-cache-block-size, etc */+#define CACHE_TYPE_INSTRUCTION 2+#define CACHE_TYPE_DATA 3staticconststructcache_type_infocache_type_info[]={{+/* Embedded systems that use cache-size, cache-block-size,+*etc.fortheUnified(typicallyL2)cache.*/+.name="Unified",+.size_prop="cache-size",+.line_size_props={"cache-line-size",+"cache-block-size",},+.nr_sets_prop="cache-sets",+},+{/* PowerPC Processor binding says the [di]-cache-**mustbeequalonunifiedcaches,sojustuse*d-cacheproperties.*/
From: Dave Olson <redacted>
This is version 5 of the patch, incorporating Michael Ellerman's
suggested changes from March 26, 2015. v5 removes the __cpuinit
that had crept in from my patch based on an older kernel, but is
otherwise the same as v4.
================
This problem appears to have been introduced in 2.6.29 by
the commit in the Fixes line below.
This 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
Some embedded powerpc systems use cache-size in DTS for the unified L2 cache
size, not d-cache-size, so we need to allow for both DTS names. Added a
new CACHE_TYPE_UNIFIED_D cache_type_info structure to handle this.
Fixes: 93197a36a9c16a85fb24cf5a8639f7bf9af838a3
Signed-off-by: Dave Olson <redacted>
---
arch/powerpc/kernel/cacheinfo.c | 44 ++++++++++++++++++++++++++++++---------
1 file changed, 34 insertions(+), 10 deletions(-)
@@ -61,12 +61,22 @@ struct cache_type_info {};/* These are used to index the cache_type_info array. */-#define CACHE_TYPE_UNIFIED 0-#define CACHE_TYPE_INSTRUCTION 1-#define CACHE_TYPE_DATA 2+#define CACHE_TYPE_UNIFIED 0 /* cache-size, cache-block-size, etc. */+#define CACHE_TYPE_UNIFIED_D 1 /* d-cache-size, d-cache-block-size, etc */+#define CACHE_TYPE_INSTRUCTION 2+#define CACHE_TYPE_DATA 3staticconststructcache_type_infocache_type_info[]={{+/* Embedded systems that use cache-size, cache-block-size,+*etc.fortheUnified(typicallyL2)cache.*/+.name="Unified",+.size_prop="cache-size",+.line_size_props={"cache-line-size",+"cache-block-size",},+.nr_sets_prop="cache-sets",+},+{/* PowerPC Processor binding says the [di]-cache-**mustbeequalonunifiedcaches,sojustuse*d-cacheproperties.*/