From owner-freebsd-ia64@FreeBSD.ORG Sun Jan 30 10:57:20 2005 Return-Path: Delivered-To: freebsd-ia64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 024B316A4CF for ; Sun, 30 Jan 2005 10:57:20 +0000 (GMT) Received: from itchy.rabson.org (mailgate.nlsystems.com [80.177.232.242]) by mx1.FreeBSD.org (Postfix) with ESMTP id C731043D4C for ; Sun, 30 Jan 2005 10:57:18 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from ns0.nlsystems.com (ns0.nlsystems.com [80.177.232.243]) by itchy.rabson.org (8.12.11/8.12.11) with ESMTP id j0UAvD5w087933; Sun, 30 Jan 2005 10:57:13 GMT (envelope-from dfr@nlsystems.com) From: Doug Rabson To: freebsd-ia64@freebsd.org Date: Sun, 30 Jan 2005 10:57:07 +0000 User-Agent: KMail/1.7.1 References: <41FA27AD.4030208@hob.de> In-Reply-To: <41FA27AD.4030208@hob.de> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200501301057.08334.dfr@nlsystems.com> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on itchy.rabson.org X-Virus-Scanned: clamd / ClamAV version 0.75.1, clamav-milter version 0.75c on itchy.rabson.org X-Virus-Status: Clean Subject: Re: TLB miss handlers X-BeenThere: freebsd-ia64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the IA-64 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 30 Jan 2005 10:57:20 -0000 On Friday 28 January 2005 11:53, Christian Hildner wrote: > Hi, > > looking at entry 0x0400 of the interrupt table I am wondering about > the following lines: > > IVT_ENTRY(Instruction_TLB, 0x0400) > mov r16=cr.ifa > mov r17=pr > ;; > thash r18=r16 > ttag r19=r16 > ;; > add r21=16,r18 // tag > add r20=24,r18 // collision chain > ;; > ld8 r21=[r21] // check VHPT tag > ^^^^^^^^^^ > Are you sure you cannot enter a nested TLB miss fault here on IA64 > implementations that do not have the VHPT walker implemented? You > wouldn't get fault 0x0000 since there is no walker that throws that > fault. When I wrote this originally, I had the VHPT mapped by a TR. I believe this is still the case.