From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:52013) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vjn1g-00089i-Ah for qemu-devel@nongnu.org; Fri, 22 Nov 2013 04:27:56 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vjn1X-00065t-Tz for qemu-devel@nongnu.org; Fri, 22 Nov 2013 04:27:48 -0500 Received: from mail-ea0-x232.google.com ([2a00:1450:4013:c01::232]:33964) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vjn1X-00065e-NI for qemu-devel@nongnu.org; Fri, 22 Nov 2013 04:27:39 -0500 Received: by mail-ea0-f178.google.com with SMTP id d10so384565eaj.37 for ; Fri, 22 Nov 2013 01:27:38 -0800 (PST) Sender: Paolo Bonzini Message-ID: <528F2385.50300@redhat.com> Date: Fri, 22 Nov 2013 10:27:33 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1385072461-31317-1-git-send-email-lersek@redhat.com> <1385072499-31367-1-git-send-email-lersek@redhat.com> In-Reply-To: <1385072499-31367-1-git-send-email-lersek@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [edk2] [edk2 PATCH] OvmfPkg: split the variable store to a separate file List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: edk2-devel@lists.sourceforge.net Cc: Laszlo Ersek , qemu-devel@nongnu.org, crobinso@redhat.com Il 21/11/2013 23:21, Laszlo Ersek ha scritto: > Split the variable store off to a separate file when SPLIT_VARSTORE is > defined. > > Even in this case, the preexistent PCDs' values don't change. Qemu must > take care of contiguously mapping NVVARSTORE.fd + OVMF.fd so that when > concatenated they end exactly at 4GB. > > Contributed-under: TianoCore Contribution Agreement 1.0 > Signed-off-by: Laszlo Ersek It's good that this is so easy to do. The obvious question is, what happens if you only pass only OVMF.fd (which would be less than 2MB in size, right)? Also, I see a command line compatibility problem, especially if one wants OVMF.fd to become the default firmware. Then, having to specify it again on the command line would be strange. Paolo