From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-ey0-f170.google.com (mail-ey0-f170.google.com [209.85.215.170]) by ozlabs.org (Postfix) with ESMTP id 27AF9B6EDD for ; Mon, 9 Aug 2010 15:55:42 +1000 (EST) Received: by eyh6 with SMTP id 6so11383535eyh.15 for ; Sun, 08 Aug 2010 22:55:40 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <1281134958.2168.39.camel@pasglop> References: <20100805123725.63d009b1@schlenkerla.am.freescale.net> <20100805134654.70f8f787@schlenkerla.am.freescale.net> <1281134958.2168.39.camel@pasglop> Date: Sun, 8 Aug 2010 22:55:40 -0700 Message-ID: Subject: Re: Relocating bootwrapper causes kernel panic From: Shawn Jin To: Benjamin Herrenschmidt Content-Type: text/plain; charset=ISO-8859-1 Cc: Scott Wood , ppcdev List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , >> > >> I think the cause is clear now. But how to fix it? Two questions: >> > >> 2. If the DTLB miss exception handler is not the right guy to load = a >> > >> proper TLB entry, how can I set one entry based on the link_address >> > >> and the address of the flat dt blob? >> > > >> > > Given how early in the boot process it is, it's probably going to ne= ed >> > > to be handled specially. >> > >> > What APIs can I use to set up DTLBs? >> >> I don't think there is one that works on 8xx. =A0You'll could hack up >> initial_mmu, or else write some C code to insert an 8xx TLB entry. > > Yup, I think he just ends up getting out of the initial mapping which is > smallish on 8xx, no ? Might be worth sticking in one more entry during > boot... If CONFIG_PIN_TLB is on, two more entries are pinned down, which gives 16MB mappings. Just curious. Why is there only one entry by default? what's the trade-off to pin down all 4 entries? THanks, -Shawn.