Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933844Ab3CHH2x (ORCPT ); Fri, 8 Mar 2013 02:28:53 -0500 Received: from mail-pa0-f43.google.com ([209.85.220.43]:42113 "EHLO mail-pa0-f43.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753813Ab3CHH2v (ORCPT ); Fri, 8 Mar 2013 02:28:51 -0500 Date: Thu, 7 Mar 2013 23:28:46 -0800 From: Tejun Heo To: Yinghai Lu Cc: "Yu, Fenghua" , Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Andrew Morton , Thomas Renninger , Tang Chen , linux-kernel@vger.kernel.org, Pekka Enberg , Jacob Shin , "Rafael J. Wysocki" , linux-acpi@vger.kernel.org Subject: Re: [PATCH 04/14] x86, ACPI: make acpi override finding work with 32bit flat mode Message-ID: <20130308072846.GQ14556@mtj.dyndns.org> References: <1362718720-27048-1-git-send-email-yinghai@kernel.org> <1362718720-27048-5-git-send-email-yinghai@kernel.org> <20130308055023.GF14556@mtj.dyndns.org> <20130308070651.GN14556@mtj.dyndns.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1401 Lines: 41 On Thu, Mar 07, 2013 at 11:25:14PM -0800, Yinghai Lu wrote: > >> > Why is this table made a stack variable? What's the benefit of doing > >> > that? > >> > >> so I do need to switch global variables to phys and access it. > > > > I can't really understand what your response means. Can you please > > elaborate? > > sorry, I missed NOT. > > so I do NOT need to switch global variables from kernel virtual addr > to phys address and access it > in 32bit flat mode. Ah, okay, so the function is called with a completely different address mode and so you actually want to build the table on stack so that you don't have to flip the address mode for the global address. > >> yes, one for 32bit from head_32.S, phys. > >> one for 64bit from head64.c. with _va. > > > > head64.c can't call with phys? Why not? > > HPA's #PF set up page table only handle kernel low mapping address. > > and after reset_early_page_tables, only kernel high mapping address is > there. and other low mapping will be supported via #PF handler. Okay, it now makes sense. Ah.... You'll definitely need a lot of documentation explanining what's going on. Thanks. -- tejun -- 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/