public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: x86@kernel.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: x86: add new cache descriptors
Date: Tue, 10 Nov 2009 13:59:44 -0500	[thread overview]
Message-ID: <20091110185944.GA20935@redhat.com> (raw)
In-Reply-To: <20091110184924.GA20337@redhat.com>

On Tue, Nov 10, 2009 at 01:49:24PM -0500, Dave Jones wrote:
 
 > diff --git a/arch/x86/kernel/cpu/intel_cacheinfo.c b/arch/x86/kernel/cpu/intel_cacheinfo.c
 > index 804c40e..228fc67 100644
 > --- a/arch/x86/kernel/cpu/intel_cacheinfo.c
 > +++ b/arch/x86/kernel/cpu/intel_cacheinfo.c
 > @@ -102,6 +102,9 @@ static const struct _cache_table __cpuinitconst cache_table[] =
 >  	{ 0xe2, LVL_3,    2048 },	/* 16-way set assoc, 64 byte line size */
 >  	{ 0xe3, LVL_3,    4096 },	/* 16-way set assoc, 64 byte line size */
 >  	{ 0xe4, LVL_3,    8192 },	/* 16-way set assoc, 64 byte line size */
 > +	{ 0xea, LVL_3,    12288 },	/* 24-way set assoc, 64 byte line size */
 > +	{ 0xeb, LVL_3,    18432 },	/* 24-way set assoc, 64 byte line size */
 > +	{ 0xec, LVL_3,    24576 },	/* 24-way set assoc, 64 byte line size */
 >  	{ 0x00, 0, 0}

btw, something I'm thinking of doing as a followup is making these use the
defines like we have in drivers/char/agp/agp.h

#define KB(x)   ((x) * 1024)
#define MB(x)   (KB (KB (x)))
#define GB(x)   (MB (KB (x)))

There's a few similar definitions throughout the tree.  Any opinions on whether
I should add these to kernel.h, or create a new header for them ?

	Dave


  reply	other threads:[~2009-11-10 19:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-10 18:49 x86: add new cache descriptors Dave Jones
2009-11-10 18:59 ` Dave Jones [this message]
2009-11-10 19:09 ` [tip:x86/urgent] x86: Add new Intel CPU cache size descriptors tip-bot for Dave Jones

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=20091110185944.GA20935@redhat.com \
    --to=davej@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=x86@kernel.org \
    /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