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.10703.1637836696476146218
 for <devel@edk2.groups.io>;
 Thu, 25 Nov 2021 02:38:16 -0800
Authentication-Results: mx.groups.io;
 dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=apzo9XBM;
 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=1637836695;
	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=XTERmKsLUNgJQwKAujsT/m3iZOR0GcFfXzf21TDhH+U=;
	b=apzo9XBMxqc5PB3ITqrEVkVsEAFEkTKJZgWo1G6eA1Qr6RW9mcxrXY6ik9Pd68cLsLwfkb
	mFqiYk0Lw0nWQwVtabDIX+/BsbEuai5E2p0pT8KSD6YQk0hRWpC+bJ9A4Zwbh2hm0GcakL
	0uMAzXBSVv9oUxBQK4UYerwcvx60nt8=
Received: from mimecast-mx01.redhat.com (mimecast-mx01.redhat.com
 [209.132.183.4]) by relay.mimecast.com with ESMTP with STARTTLS
 (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id
 us-mta-393-QP8Hyj8zOOWKCO6waOZzwg-1; Thu, 25 Nov 2021 05:38:13 -0500
X-MC-Unique: QP8Hyj8zOOWKCO6waOZzwg-1
Received: from smtp.corp.redhat.com (int-mx06.intmail.prod.int.phx2.redhat.com [10.5.11.16])
	(using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by mimecast-mx01.redhat.com (Postfix) with ESMTPS id 7742581CCB4;
	Thu, 25 Nov 2021 10:38:12 +0000 (UTC)
Received: from sirius.home.kraxel.org (unknown [10.39.192.79])
	by smtp.corp.redhat.com (Postfix) with ESMTPS id 16A9A79459;
	Thu, 25 Nov 2021 10:38:12 +0000 (UTC)
Received: by sirius.home.kraxel.org (Postfix, from userid 1000)
	id 32CCB1800991; Thu, 25 Nov 2021 11:38:10 +0100 (CET)
Date: Thu, 25 Nov 2021 11:38:10 +0100
From: "Gerd Hoffmann" <kraxel@redhat.com>
To: maobibo <maobibo@loongson.cn>
Cc: devel@edk2.groups.io
Subject: Re: one possible issue with ovmf fvb
Message-ID: <20211125103810.qtydjqvysuvak5c4@sirius.home.kraxel.org>
References: <444f3f42-cc2c-f255-389e-504b31789fcd@loongson.cn>
MIME-Version: 1.0
In-Reply-To: <444f3f42-cc2c-f255-389e-504b31789fcd@loongson.cn>
X-Scanned-By: MIMEDefang 2.79 on 10.5.11.16
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

  Hi,

>   PcdStatus = PcdSet64S (PcdFlashNvStorageVariableBase64, (UINT32)(UINTN) Ptr);
>   ASSERT_RETURN_ERROR (PcdStatus);

I guess you are referring to that UINT32 cast?
Not sure why it is there.  I think you can just drop it.

> Can uefi bios manage memory beyond 4G?

The X64 builds can do that just fine, although they usually store
everything below 4G, so issues like the one above go unnoticed.

HTH,
  Gerd