If we have a bug which causes us to start with the wrong kind of OF
node when linking up the cache tree, it's helpful for debugging to
print information about what we found vs what we expected. So replace
uses of WARN_ON_ONCE with WARN_ONCE, which lets us include an
informative message instead of a contentless backtrace.

Signed-off-by: Nathan Lynch <nath...@linux.ibm.com>
---
 arch/powerpc/kernel/cacheinfo.c | 10 ++++++++--
 1 file changed, 8 insertions(+), 2 deletions(-)

diff --git a/arch/powerpc/kernel/cacheinfo.c b/arch/powerpc/kernel/cacheinfo.c
index d8200f7e1075..30be2cdc8aa9 100644
--- a/arch/powerpc/kernel/cacheinfo.c
+++ b/arch/powerpc/kernel/cacheinfo.c
@@ -429,8 +429,14 @@ static void link_cache_lists(struct cache *smaller, struct 
cache *bigger)
 
 static void do_subsidiary_caches_debugcheck(struct cache *cache)
 {
-       WARN_ON_ONCE(cache->level != 1);
-       WARN_ON_ONCE(!of_node_is_type(cache->ofnode, "cpu"));
+       WARN_ONCE(cache->level != 1,
+                 "instantiating cache chain from L%d %s cache for "
+                 "%pOFP instead of an L1\n", cache->level,
+                 cache_type_string(cache), cache->ofnode);
+       WARN_ONCE(!of_node_is_type(cache->ofnode, "cpu"),
+                 "instantiating cache chain from node %pOFP of type '%s' "
+                 "instead of a cpu node\n", cache->ofnode,
+                 of_node_get_device_type(cache->ofnode));
 }
 
 static void do_subsidiary_caches(struct cache *cache)
-- 
2.20.1

Reply via email to