Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S262095AbTFIVQA (ORCPT ); Mon, 9 Jun 2003 17:16:00 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S262093AbTFIVP7 (ORCPT ); Mon, 9 Jun 2003 17:15:59 -0400 Received: from 66-122-194-202.ded.pacbell.net ([66.122.194.202]:43425 "HELO mail.keyresearch.com") by vger.kernel.org with SMTP id S262095AbTFIVPu (ORCPT ); Mon, 9 Jun 2003 17:15:50 -0400 Subject: Re: memtest86 on the opteron From: "Bryan O'Sullivan" To: Dave Jones Cc: Dan Carpenter , linux-kernel@vger.kernel.org, ppokorny@penguincomputing.com In-Reply-To: <20030609211823.GA2182@suse.de> References: <20030609211823.GA2182@suse.de> Content-Type: multipart/mixed; boundary="=-JXwGAmiC4/4tovDQ5iCc" Organization: Message-Id: <1055194161.32291.11.camel@serpentine.internal.keyresearch.com> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.4 Date: 09 Jun 2003 14:29:22 -0700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1637 Lines: 56 --=-JXwGAmiC4/4tovDQ5iCc Content-Type: text/plain Content-Transfer-Encoding: 7bit On Mon, 2003-06-09 at 14:18, Dave Jones wrote: > 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. This is the patch I use, which seems to make sense, since I don't know of any other steppings. No point in parameterising the code until you have some parameters.