Date: Mon, 6 Sep 1999 23:49:55 +0200 (CEST) From: Wilko Bulte <wilko@yedi.iaf.nl> To: green@FreeBSD.ORG (Brian F. Feldman) Cc: aa8vb@ipass.net, mike@smith.net.au, hackers@FreeBSD.ORG Subject: Re: K6 Write Combining & FreeBSD Message-ID: <199909062149.XAA03624@yedi.iaf.nl> In-Reply-To: <Pine.BSF.4.10.9909052024230.98872-100000@janus.syracuse.net> from "Brian F. Feldman" at "Sep 5, 1999 8:26:36 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199909062149.XAA03624>