From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:37126) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlJHm-0000AS-Cp for qemu-devel@nongnu.org; Tue, 26 Nov 2013 09:06:48 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VlJHg-0000qs-Dn for qemu-devel@nongnu.org; Tue, 26 Nov 2013 09:06:42 -0500 Received: from mx1.redhat.com ([209.132.183.28]:30015) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VlJHg-0000qn-57 for qemu-devel@nongnu.org; Tue, 26 Nov 2013 09:06:36 -0500 Message-ID: <5294AADE.6080504@redhat.com> Date: Tue, 26 Nov 2013 15:06:22 +0100 From: Paolo Bonzini MIME-Version: 1.0 References: <1385072461-31317-1-git-send-email-lersek@redhat.com> <87iovkvd8t.fsf@blackfin.pond.sub.org> <528FA2AB.2040806@redhat.com> <871u244ic6.fsf@blackfin.pond.sub.org> <5293A8CF.1000602@redhat.com> <5294A4F0.1020608@redhat.com> <5294A7D1.1000501@redhat.com> In-Reply-To: <5294A7D1.1000501@redhat.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [edk2] [qemu PATCH] hw/i386/pc_sysfw: support more than one flash drive List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Laszlo Ersek Cc: "Jordan Justen (Intel address)" , crobinso@redhat.com, edk2-devel@lists.sourceforge.net, Markus Armbruster , qemu-devel@nongnu.org Il 26/11/2013 14:53, Laszlo Ersek ha scritto: >> > >> > IIUC in the case of OVMF the guest "just knows" that there are multiple >> > devices backing the range. Is that right? > No, the guest (the flash driver) is unaware of that. It could know if it > wanted to, but it doesn't care. It cares about a base address and a > size, and that range is subdivided into various roles. But how many > flash devices back the range is not interesting for the driver. > > Jordan wrote the driver with one flash device in mind, and when I split > the image in two parts, I took care to map them so that the base > address, the size, and those boundaries stay the same. It's sufficient > for the driver to continue working. Ah, I see it now. That's because the driver never needs to write an offset into the flash device. Offsets are communicated by writing to different memory addresses. Since the OVMF driver never queries the size of the device, it doesn't care whether the flash is one or two. Paolo