From: Thomas Gleixner <tglx@linutronix.de>
To: Dave Hansen <dave.hansen@intel.com>
Cc: Vikas Shivappa <vikas.shivappa@linux.intel.com>,
linux-kernel@vger.kernel.org, vikas.shivappa@intel.com,
hpa@zytor.com, mingo@kernel.org, tj@kernel.org,
matt.flemming@intel.com, will.auld@intel.com,
peterz@infradead.org
Subject: Re: [PATCH] x86: Intel Cache Allocation Technology support
Date: Fri, 21 Nov 2014 21:43:34 +0100 (CET) [thread overview]
Message-ID: <alpine.DEB.2.11.1411212139360.6439@nanos> (raw)
In-Reply-To: <546FA0C4.1000402@intel.com>
On Fri, 21 Nov 2014, Dave Hansen wrote:
> On 11/19/2014 05:05 PM, Vikas Shivappa wrote:
> > + /*
> > + * Hard code the checks and values for HSW SKUs.
> > + * Unfortunately! have to check against only these brand name strings.
> > + */
> > +
> > + for (i = 0; i < 5; i++)
> > + if (!strcmp(hsw_brandstrs[i], c->x86_model_id)) {
> > + c->x86_cqe_closs = 4;
> > + c->x86_cqe_cbmlength = 20;
> > + return true;
> > + }
>
> Please use ARRAY_SIZE() here. Otherwise, I guarantee the next string
> you add to hsw_brandstrs[] gets silently ignored.
>
> Are there really only 5 CPUs? This:
>
> > http://ark.intel.com/products/family/78583/Intel-Xeon-Processor-E5-v3-Family#@Server
>
> lists 32 skus.
We really should find a proper software probing solution for this
instead of having a gazillion of brand strings plus micro code version
checks around for this.
Why cant the HW folks release a micro code version which fixes the
obviously wreckaged CPUID enumeration of this feature instead of
burdening us with that horror?
Can you please find a proper sized clue bat and whack your HW folks
over the head for this insanity?
Thanks,
tglx
next prev parent reply other threads:[~2014-11-21 20:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-20 1:05 Vikas Shivappa
2014-11-21 14:19 ` Thomas Gleixner
2014-11-21 20:00 ` Vikas Shivappa
2014-11-21 20:15 ` Borislav Petkov
2014-11-21 21:14 ` Vikas Shivappa
2014-11-23 20:04 ` Thomas Gleixner
2014-11-24 9:36 ` Shivappa, Vikas
2014-11-23 19:26 ` Matt Fleming
2014-11-23 19:29 ` Thomas Gleixner
2014-11-24 9:44 ` Shivappa, Vikas
2014-11-26 0:01 ` Shivappa, Vikas
2014-11-26 0:05 ` Shivappa, Vikas
2014-11-21 20:29 ` Dave Hansen
2014-11-21 20:43 ` Thomas Gleixner [this message]
2014-11-21 21:27 ` Vikas Shivappa
2014-11-21 21:25 ` Vikas Shivappa
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=alpine.DEB.2.11.1411212139360.6439@nanos \
--to=tglx@linutronix.de \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.flemming@intel.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tj@kernel.org \
--cc=vikas.shivappa@intel.com \
--cc=vikas.shivappa@linux.intel.com \
--cc=will.auld@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®