Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Tue, 27 Aug 2002 16:41:24 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Tue, 27 Aug 2002 16:41:24 -0400 Received: from ppp-217-133-221-79.dialup.tiscali.it ([217.133.221.79]:60108 "EHLO home.ldb.ods.org") by vger.kernel.org with ESMTP id ; Tue, 27 Aug 2002 16:41:23 -0400 Subject: Re: [PATCH] M386 flush_one_tlb invlpg From: Luca Barbieri To: Linus Torvalds Cc: Hugh Dickins , Dave Jones , Marc Dietrich , Linux-Kernel ML In-Reply-To: References: Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="=-+fyxyEv1+wipM/Ld/Wa6" X-Mailer: Ximian Evolution 1.0.5 Date: 27 Aug 2002 22:45:29 +0200 Message-Id: <1030481129.6203.3.camel@ldb> Mime-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1055 Lines: 31 --=-+fyxyEv1+wipM/Ld/Wa6 Content-Type: text/plain Content-Transfer-Encoding: 7bit > There's another issue, which is the fact that I do not believe that invlpg > is even guaranteed to invalidate a G page at all - although obviously all > current CPU's seem to work that way. However, I don't see that documented > anywhere. You haven't read the P4 system architecture manual, section 3.11. It explicitly says that invlpg ignores the G flag. --=-+fyxyEv1+wipM/Ld/Wa6 Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) iD8DBQA9a+Tpdjkty3ft5+cRAqB4AJ4luCRj55sPrngbvtVLgHfeowaWZACfbUv4 ahy/vrMcz/Qa/vOUMSweTrE= =Xutp -----END PGP SIGNATURE----- --=-+fyxyEv1+wipM/Ld/Wa6-- - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/