From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:54100) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ceNDb-0001YY-3D for qemu-devel@nongnu.org; Thu, 16 Feb 2017 09:39:36 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ceNDW-0002lx-CW for qemu-devel@nongnu.org; Thu, 16 Feb 2017 09:39:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:54434) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1ceNDW-0002le-6z for qemu-devel@nongnu.org; Thu, 16 Feb 2017 09:39:30 -0500 References: <1487255413-14196-1-git-send-email-fred.konrad@greensocs.com> From: Paolo Bonzini Message-ID: <854a99a2-015e-5c6b-1f72-1aa189194084@redhat.com> Date: Thu, 16 Feb 2017 15:39:26 +0100 MIME-Version: 1.0 In-Reply-To: <1487255413-14196-1-git-send-email-fred.konrad@greensocs.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [PATCH V1 0/7] execute code from mmio area List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: fred.konrad@greensocs.com, qemu-devel@nongnu.org Cc: peter.maydell@linaro.org, edgar.iglesias@xilinx.com, alistair.francis@xilinx.com, clg@kaod.org, mark.burton@greensocs.com On 16/02/2017 15:30, fred.konrad@greensocs.com wrote: > From: KONRAD Frederic > > This series allows to execute code from mmio areas. > The main goal of this is to be able to run code for example from an SPI device. > > The three first patch fixes the way get_page_addr_code fills the TLB. > > The fourth patch implements the mmio execution helpers: the device must > implement the request_ptr callback of the MemoryRegion and will be notified when > the guest wants to execute code from it. > > The fifth patch introduces mmio_interface device which allows to dynamically > map a host pointer somewhere into the memory. > > The sixth patch implements the execution from the SPI memories in the > xilinx_spips model. Sorry for the stupid question, where is mmio-interface used? Wrong version of patch 7 perhaps? Paolo > Thanks, > Fred > > RFC -> V1: > * Use an interface (mmio-interface) to fix any reference leak issue. > > KONRAD Frederic (7): > cputlb: cleanup get_page_addr_code to use VICTIM_TLB_HIT > cputlb: move get_page_addr_code > cputlb: fix the way get_page_addr_code fills the tlb > exec: allow to get a pointer for some mmio memory region > qdev: add MemoryRegion property > introduce mmio_interface > xilinx_spips: allow mmio execution > > cputlb.c | 81 ++++++++++++++----------- > hw/misc/Makefile.objs | 1 + > hw/misc/mmio_interface.c | 128 +++++++++++++++++++++++++++++++++++++++ > hw/ssi/xilinx_spips.c | 74 ++++++++++++++++------ > include/exec/memory.h | 35 +++++++++++ > include/hw/misc/mmio_interface.h | 49 +++++++++++++++ > include/hw/qdev-properties.h | 2 + > memory.c | 57 +++++++++++++++++ > 8 files changed, 372 insertions(+), 55 deletions(-) > create mode 100644 hw/misc/mmio_interface.c > create mode 100644 include/hw/misc/mmio_interface.h >