From owner-freebsd-hackers Mon Sep 6 15:32:36 1999 Delivered-To: freebsd-hackers@freebsd.org Received: from uni4nn.gn.iaf.nl (osmium.gn.iaf.nl [193.67.144.12]) by hub.freebsd.org (Postfix) with ESMTP id 1DAE414DE0; Mon, 6 Sep 1999 15:32:28 -0700 (PDT) (envelope-from wilko@yedi.iaf.nl) Received: from yedi.iaf.nl (uucp@localhost) by uni4nn.gn.iaf.nl (8.9.2/8.9.2) with UUCP id AAA13443; Tue, 7 Sep 1999 00:17:31 +0200 (MET DST) Received: (from wilko@localhost) by yedi.iaf.nl (8.9.3/8.9.3) id XAA03624; Mon, 6 Sep 1999 23:49:55 +0200 (CEST) (envelope-from wilko) From: Wilko Bulte Message-Id: <199909062149.XAA03624@yedi.iaf.nl> Subject: Re: K6 Write Combining & FreeBSD In-Reply-To: from "Brian F. Feldman" at "Sep 5, 1999 8:26:36 pm" To: green@FreeBSD.ORG (Brian F. Feldman) Date: Mon, 6 Sep 1999 23:49:55 +0200 (CEST) Cc: aa8vb@ipass.net, mike@smith.net.au, hackers@FreeBSD.ORG X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-pgp-info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4ME+ PL43 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG As Brian F. Feldman wrote ... > On Sun, 5 Sep 1999, Randall Hopper wrote: > > > Mike Smith: > > |> Also, I wonder if you've seen/heard of an MTRR patch for 3.2-RELEASE > > | > > |You could try to backport the two sets of commits I just made to the > > |-stable branch, but you might be better off moving to -stable or to > > |3.3-RELEASE. > > > > Ok, I might try that. From Brian's message, it sounds like he's made some > > commits for MTRR. Would I need those as well (or are your commits the work > > he spoke of). > > It may be worth specifying that k6_mem.c should be disabled in RELENG_3 pending > further investigation of problems with the MTRR interfeace (i.e. that it can > corrupt other memory...) For now, it's unsafe. Maybe I'm missing the point here, but as a AMD user I'm interested anyway: 'should be disabled', does that mean one has to 'hand hack' to disable it? Stable being -stable I'd have guessed it should be disabled by default if it is not 100% working like it should. TIA -- | / o / / _ Arnhem, The Netherlands - Powered by FreeBSD - |/|/ / / /( (_) Bulte WWW : http://www.tcja.nl http://www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message