From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:46374) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X5mKQ-0001Qp-UE for qemu-devel@nongnu.org; Fri, 11 Jul 2014 21:42:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1X5mKJ-0000UT-Eh for qemu-devel@nongnu.org; Fri, 11 Jul 2014 21:42:18 -0400 Received: from mail-wi0-f179.google.com ([209.85.212.179]:59796) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1X5mKJ-0000T0-9C for qemu-devel@nongnu.org; Fri, 11 Jul 2014 21:42:11 -0400 Received: by mail-wi0-f179.google.com with SMTP id cc10so76116wib.12 for ; Fri, 11 Jul 2014 18:42:10 -0700 (PDT) From: Nikolay Nikolaev Date: Sat, 12 Jul 2014 04:42:02 +0300 Message-ID: <20140712014119.10636.81503.stgit@3820> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Subject: [Qemu-devel] [PATCH v2 0/2 for-2.1] vhost-user fixes List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: snabb-devel@googlegroups.com, qemu-devel@nongnu.org, mst@redhat.com Cc: tech@virtualopensystems.com, n.nikolaev@virtualopensystems.com The latest vhost-user changes changed the VHOST_SET_MEM_TABLE handling. Now the memory regions are mapped from dev->mem. There is an error when calling qemu_get_ram_fd with reg->guest_phys_addr. The right approach is to find the ram_addr_t corresponding to the userspace_addr using qemu_ram_addr_from_host first. Thanks to Paolo Bonzini for poinitng the real problem. The related vhost-user qtest is also updated to reflect the changes in vhost-user message structures. Changes since v1: - dropped the patches 1 and 2 and just fixed the "real issue" --- Nikolay Nikolaev (2): vhost-user: Fix VHOST_SET_MEM_TABLE processing qtest: Adapt vhost-user-test to latehs vhost-user changes hw/virtio/vhost-user.c | 4 +++- tests/vhost-user-test.c | 11 +++++++++-- 2 files changed, 12 insertions(+), 3 deletions(-) -- Signature