From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by mx.groups.io with SMTP id smtpd.web10.46599.1653983125112917555 for ; Tue, 31 May 2022 00:45:25 -0700 Authentication-Results: mx.groups.io; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=Nt/o0Xpt; spf=pass (domain: redhat.com, ip: 170.10.129.124, mailfrom: kraxel@redhat.com) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1653983124; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=/TCwM3JCMaTbGjHzHXZuHGuzxvbawKgHrHCBJVT+lwo=; b=Nt/o0XptisUAhYrl8Pm6cCbXvsyKHcPuNyize/4b66/vzh4xgicVMDZGOgqONtg1Pdw5+K T+J7K7oSKbrTSrwV7yLfTrpd5LNwA6u9WVSoxWIvssxbNoAVYTKBbNuiY38VLwTgLSDLZs rYGCbPZ6B6Y6MEC+IxiP+Q2xkz8l/lU= Received: from mimecast-mx02.redhat.com (mx3-rdu2.redhat.com [66.187.233.73]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-627-Ry6cRLYXNquNFA2DqzISXw-1; Tue, 31 May 2022 03:45:16 -0400 X-MC-Unique: Ry6cRLYXNquNFA2DqzISXw-1 Received: from smtp.corp.redhat.com (int-mx01.intmail.prod.int.rdu2.redhat.com [10.11.54.1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 13EAE1C0897C; Tue, 31 May 2022 07:45:16 +0000 (UTC) Received: from sirius.home.kraxel.org (unknown [10.39.192.41]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 9A1C140CFD0A; Tue, 31 May 2022 07:45:15 +0000 (UTC) Received: by sirius.home.kraxel.org (Postfix, from userid 1000) id F39EC180039C; Tue, 31 May 2022 09:45:13 +0200 (CEST) Date: Tue, 31 May 2022 09:45:13 +0200 From: "Gerd Hoffmann" To: devel@edk2.groups.io, zhiguang.liu@intel.com Cc: Guo Dong , Ray Ni , Maurice Ma , Benjamin You , Sean Rhodes Subject: Re: [edk2-devel] [PATCH] UefiPayloadPkg: Always split page table entry to 4K if it covers stack. Message-ID: <20220531074513.fciegyxkrgiwwqem@sirius.home.kraxel.org> References: <20220531053937.19696-1-zhiguang.liu@intel.com> MIME-Version: 1.0 In-Reply-To: <20220531053937.19696-1-zhiguang.liu@intel.com> X-Scanned-By: MIMEDefang 2.84 on 10.11.54.1 Authentication-Results: relay.mimecast.com; auth=pass smtp.auth=CUSA124A263 smtp.mailfrom=kraxel@redhat.com X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, May 31, 2022 at 01:39:37PM +0800, Zhiguang Liu wrote: > There is a concern case that stack and a proteced DXE memory range is in > the same 2M Page Table entry, and somehow CPU doesn't flash the page > table entry cache for stack, and causes Page fault when using stack. Can you clarify the "somehow" please? Are we discussing a workaround for a cpu bug here? If not this sounds like a tlbflush instruction is missing somewhere ... take care, Gerd