From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:44153) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bnLgU-00083o-Gc for qemu-devel@nongnu.org; Fri, 23 Sep 2016 04:18:15 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bnLgQ-00084a-8z for qemu-devel@nongnu.org; Fri, 23 Sep 2016 04:18:13 -0400 Received: from mx1.redhat.com ([209.132.183.28]:41020) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bnLgQ-00084G-2D for qemu-devel@nongnu.org; Fri, 23 Sep 2016 04:18:10 -0400 References: <877fa5aiu4.fsf@dusky.pond.sub.org> <6373e011-5068-b0ae-5672-e3704af556d9@redhat.com> <87h998nvf6.fsf@dusky.pond.sub.org> <6280ba63-cbe9-c2d3-ba8f-7de1369f059e@redhat.com> <87vaxojgqw.fsf@dusky.pond.sub.org> <87ponvxcit.fsf@dusky.pond.sub.org> From: Paolo Bonzini Message-ID: <7046636c-a89b-2991-083f-bf73bb29f070@redhat.com> Date: Fri, 23 Sep 2016 10:18:04 +0200 MIME-Version: 1.0 In-Reply-To: <87ponvxcit.fsf@dusky.pond.sub.org> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] [PATCH v11 0/8] Add a generic loader List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Markus Armbruster , Peter Maydell Cc: Peter Crosthwaite , Alistair Francis , Christopher Covington , "qemu-devel@nongnu.org Developers" On 23/09/2016 10:10, Markus Armbruster wrote: > For me, the similarity (at the conceptual level) to the persistent > memory case is striking: in both cases, we need a backend to manage > memory contents. The difference is that for persistent memory, changes > persist, while for the loader, they get reverted at reset. Not just that. For persistent memory, there is a MemoryRegion corresponding to the memory _and_ an interface to manage it. For the loader the contents are copied every time from an out-of-band storage. > An argument for using -device could go as follows: this is a device to > monkey patch memory. It needs a backend to manage the bits, just like > other memory-related devices do. Since its backend is trivial, we > folded it in rather than make it a separate backend. The backend is not just trivial, it is _literally_ a 64-bit value... I think "-object long,value=3D0x123456789abcdef0 is taking things a bit too= far. Paolo > If we decide to use this argument for the present interface design, I > want it recorded in the code and commit messages.