From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) (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 9FDF621A134BB for ; Wed, 3 May 2017 06:44:24 -0700 (PDT) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 106BF80471; Wed, 3 May 2017 13:44:24 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 106BF80471 Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com Authentication-Results: ext-mx04.extmail.prod.ext.phx2.redhat.com; spf=pass smtp.mailfrom=kraxel@redhat.com DKIM-Filter: OpenDKIM Filter v2.11.0 mx1.redhat.com 106BF80471 Received: from nilsson.home.kraxel.org (ovpn-116-124.ams2.redhat.com [10.36.116.124]) by smtp.corp.redhat.com (Postfix) with ESMTP id B6C6D18EC0; Wed, 3 May 2017 13:44:23 +0000 (UTC) Received: by nilsson.home.kraxel.org (Postfix, from userid 500) id 38D8F80DE7; Wed, 3 May 2017 15:44:22 +0200 (CEST) Message-ID: <1493819062.8581.177.camel@redhat.com> From: Gerd Hoffmann To: Laszlo Ersek Cc: "Kinney, Michael D" , "Fan, Jeff" , "Yao, Jiewen" , edk2-devel-01 , Paolo Bonzini Date: Wed, 03 May 2017 15:44:22 +0200 In-Reply-To: <159c4eae-4e13-7958-59f4-dfab4c1bf16e@redhat.com> References: <1382eb04-9646-133b-9ce5-8293cb54745f@redhat.com> <1493794647.8581.144.camel@redhat.com> <159c4eae-4e13-7958-59f4-dfab4c1bf16e@redhat.com> Mime-Version: 1.0 X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Wed, 03 May 2017 13:44:24 +0000 (UTC) Subject: Re: SMRAM sizes on large hosts X-BeenThere: edk2-devel@lists.01.org X-Mailman-Version: 2.1.22 Precedence: list List-Id: EDK II Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 03 May 2017 13:44:24 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi, > I propose the following: add a new fw_cfg file which communicates how > much memory (how many megabytes) the "11b" value in the tseg size > register will configure. I'd prefer to keep fw_cfg out of the picture, and I think we can do it without too much problems. We have a TSEGMB (tseg memory base) register. qemu doesn't implement it (but I think you can write to it and read back what you've written). We could make qemu update that register in case "11b" is written to the tseg size. The firmware then can read TSEGMB and figure whenever a large tseg is supported and if so how big it is. cheers, Gerd