Commit adcbdd70 authored by Vikas Shivappa's avatar Vikas Shivappa Committed by Thomas Gleixner

x86/intel_rdt: Fix padding when resource is enabled via mount

Currently max width of 'resource name' and 'resource data' is being
initialized based on 'enabled resources' during boot. But the mount can
enable different capable resources at a later time which upsets the
tabular format of schemata. Fix this to be based on 'all capable'
resources.
Signed-off-by: default avatarVikas Shivappa <vikas.shivappa@linux.intel.com>
Tested-by: default avatarPrakhya, Sai Praneeth <sai.praneeth.prakhya@intel.com>
Cc: fenghua.yu@intel.com
Cc: tony.luck@intel.com
Cc: ravi.v.shankar@intel.com
Cc: vikas.shivappa@intel.com
Link: http://lkml.kernel.org/r/1492645804-17465-2-git-send-email-vikas.shivappa@linux.intel.comSigned-off-by: default avatarThomas Gleixner <tglx@linutronix.de>
parent a83827d0
...@@ -492,7 +492,7 @@ static __init void rdt_init_padding(void) ...@@ -492,7 +492,7 @@ static __init void rdt_init_padding(void)
struct rdt_resource *r; struct rdt_resource *r;
int cl; int cl;
for_each_enabled_rdt_resource(r) { for_each_capable_rdt_resource(r) {
cl = strlen(r->name); cl = strlen(r->name);
if (cl > max_name_width) if (cl > max_name_width)
max_name_width = cl; max_name_width = cl;
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment