[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20150519203525.GQ4641@pd.tnic>
Date: Tue, 19 May 2015 22:35:25 +0200
From: Borislav Petkov <bp@...en8.de>
To: Vikas Shivappa <vikas.shivappa@...el.com>
Cc: Thomas Gleixner <tglx@...utronix.de>,
Vikas Shivappa <vikas.shivappa@...ux.intel.com>,
x86@...nel.org, linux-kernel@...r.kernel.org, hpa@...or.com,
mingo@...nel.org, tj@...nel.org, peterz@...radead.org,
Matt Fleming <matt.fleming@...el.com>,
"Auld, Will" <will.auld@...el.com>, peter.zijlstra@...el.com,
h.peter.anvin@...el.com,
"Juvva, Kanaka D" <kanaka.d.juvva@...el.com>, mtosatti@...hat.com
Subject: Re: [PATCH 2/7] x86/intel_rdt: Adds support for Class of service
management
On Tue, May 19, 2015 at 10:33:55AM -0700, Vikas Shivappa wrote:
> Yes the max bitmask and max closid can be read from cpuid. the presence of
> rdt and l3 cache alloc is indicated by rdt and cat_l3 in /proc/cpuinfo. So
> even if this message gets overwritten , user can see the feature enabled in
> kernel.
>
> Can be modified somthing similar to "Intel cache allocation enabled" as well.
Yeah, that would have more value to the user than a cryptic message
about closids and bitmask length.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists