From mboxrd@z Thu Jan 1 00:00:00 1970 From: Will Deacon Subject: Re: [PATCH kvmtool v2 0/6] arm: Add support for firmware booting Date: Tue, 22 Jan 2019 07:10:26 +0000 Message-ID: <20190122071024.GB10214@brain-police> References: <1547130046-14729-1-git-send-email-julien.thierry@arm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: andre.przywara@arm.com, Sami.Mujawar@arm.com, kvmarm@lists.cs.columbia.edu, kvm@vger.kernel.org To: Julien Thierry Return-path: Content-Disposition: inline In-Reply-To: <1547130046-14729-1-git-send-email-julien.thierry@arm.com> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu List-Id: kvm.vger.kernel.org Hi Julien, On Thu, Jan 10, 2019 at 02:20:40PM +0000, Julien Thierry wrote: > This series is based on the virtio reset series[1] posted earlier. > > We would like to be able to load firmwares like UEFI in kvmtool. > > The series contains: > A way to load the firmware into RAM and an option to be able to create > non-volatile memory zones and load data into them. > > Those non-volatile memory are presented throught the DT with a node: > > @ { > compatible = "kvmtool,flash"; > reg = < >; > label = ; > } > > These are expected to be dealt with by specific kvmtool driver and not > to be picked up by existing drivers (although technically it is just > plain memory, mapped in the guest). I've picked up the first four patches of this series, but I don't really understand where you're going with the non-volatile memory part and whether it's nvram, flash or something completely different. Given that Linux doesn't support your binding, is this something that UEFI currently uses? Will