From owner-freebsd-current  Fri Nov 22  8:24:54 2002
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 358DD37B401; Fri, 22 Nov 2002 08:24:53 -0800 (PST)
Received: from MX2.estpak.ee (mta1.mail.neti.ee [194.126.101.123])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id DB96543E9C; Fri, 22 Nov 2002 08:24:51 -0800 (PST)
	(envelope-from kalts@estpak.ee)
Received: from tiiu.internal (80-235-34-142-dsl.mus.estpak.ee [80.235.34.142])
	by MX2.estpak.ee (Postfix) with ESMTP
	id 4DB64735E3; Fri, 22 Nov 2002 18:23:46 +0200 (EET)
Received: from tiiu.internal (localhost [127.0.0.1])
	by tiiu.internal (8.12.6/8.12.6) with ESMTP id gAMGOisl003216;
	Fri, 22 Nov 2002 18:24:44 +0200 (EET)
	(envelope-from vallo@tiiu.internal)
Received: (from vallo@localhost)
	by tiiu.internal (8.12.6/8.12.6/Submit) id gAMGOhJm003215;
	Fri, 22 Nov 2002 18:24:43 +0200 (EET)
	(envelope-from vallo)
Date: Fri, 22 Nov 2002 18:24:43 +0200
From: Vallo Kallaste <kalts@estpak.ee>
To: John Baldwin <jhb@FreeBSD.org>
Cc: Terry Lambert <tlambert2@mindspring.com>, current@FreeBSD.org,
	Scott Sipe <cscotts@mindspring.com>
Subject: Re: DP2 Fatal Trap
Message-ID: <20021122162443.GA3154@tiiu.internal>
Reply-To: kalts@estpak.ee
References: <3DDD7C44.84C0D242@mindspring.com> <XFMail.20021122105742.jhb@FreeBSD.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <XFMail.20021122105742.jhb@FreeBSD.org>
User-Agent: Mutt/1.5.1i-ja.1
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

On Fri, Nov 22, 2002 at 10:57:42AM -0500, John Baldwin
<jhb@FreeBSD.org> wrote:

> > It has an effect: writing CR3 or a TSS resulting in a changed CR3
> > will not invalidate TLB entries with the G flag set, if PGE is set
> > in CR4.
> 
> I know what PG_G does, Terry.  My question is that if DISABLE_PG_G has
> no effect on the _problems_ people are having.

I have now definitive answer for _my_ case and environment. Just
finished full package build for my workstation bundle port (92
ports), including XFree-4, KDE3, mozilla-devel and whatnot. It all
went very well running kernel which had:

DISABLE_PSE     enabled
DISABLE_PG_G    disabled

Are you interested of the reverse? Can it be that enabling
DISABLE_PSE incorporates DISABLE_PG_G somehow?
-- 

Vallo Kallaste
kalts@estpak.ee

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message