From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received-SPF: Pass (sender SPF authorized) identity=mailfrom; client-ip=34.238.86.106; helo=mail.paulo.ac; envelope-from=paulo@paulo.ac; receiver=edk2-devel@lists.01.org Received: from mail.paulo.ac (mail.paulo.ac [34.238.86.106]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ml01.01.org (Postfix) with ESMTPS id 296942215BDBD for ; Wed, 31 Jan 2018 11:00:51 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by mail.paulo.ac (Postfix) with ESMTP id F3CC8C76583; Wed, 31 Jan 2018 19:06:26 +0000 (UTC) X-Virus-Scanned: amavisd-new at paulo.ac X-Spam-Flag: NO X-Spam-Score: -1.099 X-Spam-Level: X-Spam-Status: No, score=-1.099 tagged_above=-999 required=6.31 tests=[ALL_TRUSTED=-1, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no Authentication-Results: mail.paulo.ac (amavisd-new); dkim=pass (1024-bit key) header.d=paulo.ac Received: from mail.paulo.ac ([127.0.0.1]) by localhost (mail.paulo.ac [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Xi_4ezNsVXpf; Wed, 31 Jan 2018 19:06:23 +0000 (UTC) Received: from localhost (unknown [177.97.95.14]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.paulo.ac (Postfix) with ESMTPSA id C034FC788F8; Wed, 31 Jan 2018 19:06:22 +0000 (UTC) DKIM-Filter: OpenDKIM Filter v2.11.0 mail.paulo.ac C034FC788F8 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=paulo.ac; s=default; t=1517425583; bh=ZCTRpxJTHri/3Sv9Gppeba3x94lnrjTAtHvi4Z0oN9A=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=euPUSZbqH65Ezrr0HKaA7jikhN8Oa+rzpbErrJesixexZ+ZI2LE0kwJ9/I4ucn66v mn371YDkkwE5aTg/2ufPZtS2Y8S/PWO8amklX9fKghHR+gvoH0LDaQ49L46g6Pgg3l 5QBfA+Klbs92VK2iTTs7D+P66OLIRl9yIwZQ+fhY= From: Paulo Alcantara To: "Yao\, Jiewen" , "edk2-devel\@lists.01.org" Cc: Rick Bramley , "Dong\, Eric" , Kimon Berlin , Andrew Fish , Diego Medaglia , Laszlo Ersek In-Reply-To: <74D8A39837DF1E4DA445A8C0B3885C503AAA0A80@shsmsx102.ccr.corp.intel.com> References: <74D8A39837DF1E4DA445A8C0B3885C503AA8057C@shsmsx102.ccr.corp.intel.com> <9b5d7218-2d30-1c06-451c-ec9d86161aa6@paulo.ac> <74D8A39837DF1E4DA445A8C0B3885C503AAA0A80@shsmsx102.ccr.corp.intel.com> Date: Wed, 31 Jan 2018 17:05:58 -0200 Message-ID: <87fu6lg86h.fsf@paulo.ac> MIME-Version: 1.0 Subject: Re: [RFC v5 0/8] Stack trace support in X64 exception handling X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 31 Jan 2018 19:00:52 -0000 Content-Type: text/plain "Yao, Jiewen" writes: Hi Jiewen, > ======================= > OVMF IA32: DXE worked, but SMM not. > > Since the page fault is only occurring in IA32 with no paging enabled > (default case), I suspect that when we don't have paging, we are unable > to successfully validate the memory address when it's i.e. outside SMRAM > - that is, we don't know when to stop unwinding the stack. > ======================= > > For IA32 SMM, I am a little confused. > We unconditionally setup page table for SMM, no matter it is IA32 or X64. > > If you find a SMM driver running in a page-disable environment, it means, the SMM CORE load the driver in SMRAM, but the SMM CPU driver has not rebased the CPU yet. > SMM driver is still using the PageTable/GDT/IDT setup by DXE CPU > driver, not SMM CPU driver. OK - thanks for clarifying that. > Would you please double confirm what you have observed? > > You can just check the boot log file to see if PiSmmCpu driver has run > or not. Sure. I will do it and then get back to you once I got the results. Thanks Paulo