From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pf0-f178.google.com (mail-pf0-f178.google.com [209.85.192.178]) by dpdk.org (Postfix) with ESMTP id 400469ADF for ; Tue, 10 May 2016 14:18:24 +0200 (CEST) Received: by mail-pf0-f178.google.com with SMTP id 206so5462919pfu.0 for ; Tue, 10 May 2016 05:18:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mvista-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=VMrHqTCHkgjDRbZZgxLVoayNgxlTw2ASZ1EKQXukE8s=; b=x7oVIjUnf3xEg5BgBs4iWJf+b4J1pQTY2AlMnjXmv7Sl4fhHBh8zyBBk3061s1yymU PElIgFh2cwCN7ygeGRTxDGcpyKqBLlFZou6/ap5V2VBkcZZ8Xo6m7UB5J33j9eDZUZCi 0Zb7IPWkAaJx4WA4pI31UaTmSNuQKRVMKq9msoNvJx0oTR4vj8kBR2gB6h5QrHseW5iA 8tqqYn64to3BcYFptF6zMuGqAQwiICUS4Qk6TM2X1CesxVYTeE3kj2KNpQBA0mEPWaf7 qWr0Q+E1o7wGH+KuZLw13llwCQDrVr2ZgemcRcf3ijPr5ckRkigDGfJMdTYYXv4rAWqv hKHA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc; bh=VMrHqTCHkgjDRbZZgxLVoayNgxlTw2ASZ1EKQXukE8s=; b=m1uHfExS24j+2HaCsIq38eTyMjcPfWbepSsbtxX0TQCsBaw7kSGJLy3SMp3QbiZRtu 8tS+YnS4lejS9iVvxw8NDtHD9r+Lwnpk6d96txJ7eE3wp4xWQIiph6xMM8HMUW0OGzlM ihvetFd7XQhVAYy0S5IXwvqEBQeIIxy9GvCKcdbtD3zglBvvRMWTH8jIxyYaXdhgVtWB Xguqjz+OlUP3U1F3GOR2TKruv/jkKXacYAo69nvwMpmd58O71/CpBgBziRXNPH+xO3jc 2aeSOAKCiX0bQ+JpN6N89N/NpkuEC1q+JFb9ao97itDQPhi/c+vCYKywPjJLuPvPIMov H9UA== X-Gm-Message-State: AOPr4FWhTQTyWGPC6eE+Ju2qzXEJPIWmW85Ct8D4QotM2FNnX/dp7XYTXl09Ep42e1D8/knywzb8i0gLVqOH+8H3 MIME-Version: 1.0 X-Received: by 10.98.103.28 with SMTP id b28mr58780614pfc.155.1462882703534; Tue, 10 May 2016 05:18:23 -0700 (PDT) Received: by 10.66.23.130 with HTTP; Tue, 10 May 2016 05:18:23 -0700 (PDT) In-Reply-To: <1461937456-22943-1-git-send-email-viktorin@rehivetech.com> References: <1461937456-22943-1-git-send-email-viktorin@rehivetech.com> Date: Tue, 10 May 2016 17:48:23 +0530 Message-ID: From: Santosh Shukla To: Jan Viktorin Cc: dpdk , Anatoly Burakov , David Marchand , Keith Wiles , Stephen Hemminger , "Shukla, Santosh" Content-Type: text/plain; charset=UTF-8 Subject: Re: [dpdk-dev] [PATCH 00/15] Make VFIO support independent on PCI X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 May 2016 12:18:24 -0000 On Fri, Apr 29, 2016 at 7:14 PM, Jan Viktorin wrote: > > Hello, > > here follows several patchs extracting the general VFIO code out of the > PCI + VFIO code base. Usually, it's just move and rename of functions. > The most complicated ones are: > > * eal/linux: extract setup logic out of pci_vfio_map_resource > > - separation of some setup code out of the pci_vfio_map_resource > (which is otherwise quite PCI-speicific) > - it is required by the following one > > * eal/linux: move global vfio_cfg to eal_vfio.c > > - moving the vfio_cfg global variable out of the eal_pci_vfio together with > the functions working with this variable > > Some patchs make just temporary changes to avoid breakages throughout the > patch set (dma mapping). > > I am not sure, how exactly is the mp_sync code intended to work. Should there > be just a single socket connection (no matter how many bus-systems we support)? > I assume it works this way so I've generalized the eal_pci_vfio_mp_sync. > > The vfio initialization is moved out of the rte_eal_pci_init into EAL. > > The code is now prepared for adding of other infrastructures such as the SoC > that I've introduced in [1]. I've partially done this in my workspace. > I haven't started reading patch set, we'll do so. But by referring to your initiative [1] which is non-pci SoC infra, How about binding those non-pci soc via vfio-platform-way? As because vfio-for-platform device use-case is such non-pci accelerators in SoC. is your current refactoring effort aligned towards vfio-platform direction?