From: Dave Jones <davej@codemonkey.org.uk>
To: Dan Carpenter <dcarpenter@penguincomputing.com>
Cc: linux-kernel@vger.kernel.org, ppokorny@penguincomputing.com
Subject: Re: memtest86 on the opteron
Date: Mon, 9 Jun 2003 22:18:23 +0100 [thread overview]
Message-ID: <20030609211823.GA2182@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.33.0306091320500.2640-100000@ddcarpen1.penguincompting.com>
On Mon, Jun 09, 2003 at 01:26:37PM -0700, Dan Carpenter wrote:
> --- init.c.orig Mon Jun 9 10:23:10 2003
> +++ init.c Mon Jun 9 10:25:44 2003
> @@ -402,6 +402,16 @@
> }
> l1_cache = cpu_id.cache_info[3];
> l1_cache += cpu_id.cache_info[7];
> + case 15:
> + switch(cpu_id.model) {
> + case 5:
> + cprint(LINE_CPU, 0, "AMD Opteron");
> + off = 11;
> + l1_cache = cpu_id.cache_info[3];
> + l1_cache += cpu_id.cache_info[7];
> + l2_cache = (cpu_id.cache_info[11] << 8);
> + l2_cache += cpu_id.cache_info[10];
> + }
> }
Any reason to restrict it to a single stepping ?
This means you have to upgrade memtest every time a new model
is released, which seems a bit of a pain.
Chances are it'll work fine on subsequent family 15 AMD CPUs.
Dave
next prev parent reply other threads:[~2003-06-09 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-09 20:26 memtest86 on the opteron Dan Carpenter
2003-06-09 21:18 ` Dave Jones [this message]
2003-06-09 21:29 ` Bryan O'Sullivan
2003-06-11 15:51 ` Dan Carpenter
[not found] <20030607202725.22992.qmail@email.com.suse.lists.linux.kernel>
[not found] ` <20030607214356.GF667@elf.ucw.cz.suse.lists.linux.kernel>
[not found] ` <1055040745.27939.3.camel@camp4.serpentine.com.suse.lists.linux.kernel>
2003-06-08 6:27 ` Andi Kleen
2003-06-08 6:44 ` Warren Togami
2003-06-09 16:04 ` Eric W. Biederman
-- strict thread matches above, loose matches on Subject: below --
2003-06-07 20:27 dan carpenter
2003-06-07 21:43 ` Pavel Machek
2003-06-08 2:52 ` Bryan O'Sullivan
2003-06-08 8:06 ` Pavel Machek
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=20030609211823.GA2182@suse.de \
--to=davej@codemonkey.org.uk \
--cc=dcarpenter@penguincomputing.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ppokorny@penguincomputing.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