Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp3636113pxk; Tue, 29 Sep 2020 02:08:38 -0700 (PDT) X-Google-Smtp-Source: ABdhPJziFni7+gLnG531zfn2yME6jkC20nnD6hvz3Az4+NvniQEfaupCc9WXkhswgJrHu3NizEeS X-Received: by 2002:a17:907:432b:: with SMTP id ob19mr2868734ejb.400.1601370518157; Tue, 29 Sep 2020 02:08:38 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1601370518; cv=none; d=google.com; s=arc-20160816; b=CmBn0pLRPH6ZwAoCclevKKPpHM7d9JwEo9dNxOLr5STpBHnO8qMzwVQv0vQUY0GJJ5 D+qKejMqJQVgCcpl6L6E0MGqRojLX2TBp3KTDmPKR6CYVx5mC4xdGK9A5SH1N3IdI9wb 3C5eZFKF3tTx43OZKfLlV20VDSrF+MDegaminfIHf0y0jUz7hJceZq/L06A64gBmLppW 0DKxLTO8omVczVwlO2ph4roL/3vi0qEY4tJCNy2HfWz9dC91N5ZfU6xdCnlyrWgVXaNx XkqlFLHhvVOeCrqBrIZYLia9Wlu/5HCTdhlULM6DvN7oCgc5lpVojH+yYOywlGmymbjV Kzfw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:date:subject:cc:to:from; bh=QQxFe3XJJb6fr08SBGafL/CTjwZTXL556V/CYpMcULU=; b=sg/O1AlsyKB1Xcwz54gEngkSUk1n1MyQuuIEqJz2ceE77L8cXuW1N65KZuZNItYMuE hEKLWOk4rOvT6T0bHWXQ+/nwKtcaqso2PoGgszwtcGy+Zi8zQuCBMIdg3BcwCzv6Evz4 ZwfyUDEUaft/KuCpKGrEnE/MINqyqpcaPHa2AlVVC8CcA3A5iTTL0WJE70h4QtW836WQ NrhmoPOWXuzaMXxKdCxXmLzi1EznaqHzQGU6HdhwWg+ueaV2fKHWbjo6fSvKAENiwFFF UGpzAafRtOrruXyIc1ec9qZMuqboP19VgDDJreFHOukgQP+zP+P6bZP4HCNL2e6dahcn +VsA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id c8si2264107ejx.605.2020.09.29.02.08.15; Tue, 29 Sep 2020 02:08:38 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=nxp.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727973AbgI2JEA (ORCPT + 99 others); Tue, 29 Sep 2020 05:04:00 -0400 Received: from inva020.nxp.com ([92.121.34.13]:47816 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726064AbgI2JD6 (ORCPT ); Tue, 29 Sep 2020 05:03:58 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 4E82E1A1244; Tue, 29 Sep 2020 11:03:56 +0200 (CEST) Received: from inva024.eu-rdc02.nxp.com (inva024.eu-rdc02.nxp.com [134.27.226.22]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 371D21A121A; Tue, 29 Sep 2020 11:03:56 +0200 (CEST) Received: from fsr-ub1864-111.ea.freescale.net (fsr-ub1864-111.ea.freescale.net [10.171.82.141]) by inva024.eu-rdc02.nxp.com (Postfix) with ESMTP id DCC4D2032C; Tue, 29 Sep 2020 11:03:55 +0200 (CEST) From: Diana Craciun To: alex.williamson@redhat.com, kvm@vger.kernel.org Cc: bharatb.linux@gmail.com, linux-kernel@vger.kernel.org, eric.auger@redhat.com, Diana Craciun Subject: [PATCH v5 00/10] vfio/fsl-mc: VFIO support for FSL-MC device Date: Tue, 29 Sep 2020 12:03:29 +0300 Message-Id: <20200929090339.17659-1-diana.craciun@oss.nxp.com> X-Mailer: git-send-email 2.17.1 X-Virus-Scanned: ClamAV using ClamSMTP Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org DPAA2 (Data Path Acceleration Architecture) consists in mechanisms for processing Ethernet packets, queue management, accelerators, etc. The Management Complex (mc) is a hardware entity that manages the DPAA2 hardware resources. It provides an object-based abstraction for software drivers to use the DPAA2 hardware. The MC mediates operations such as create, discover, destroy of DPAA2 objects. The MC provides memory-mapped I/O command interfaces (MC portals) which DPAA2 software drivers use to operate on DPAA2 objects. A DPRC is a container object that holds other types of DPAA2 objects. Each object in the DPRC is a Linux device and bound to a driver. The MC-bus driver is a platform driver (different from PCI or platform bus). The DPRC driver does runtime management of a bus instance. It performs the initial scan of the DPRC and handles changes in the DPRC configuration (adding/removing objects). All objects inside a container share the same hardware isolation context, meaning that only an entire DPRC can be assigned to a virtual machine. When a container is assigned to a virtual machine, all the objects within that container are assigned to that virtual machine. The DPRC container assigned to the virtual machine is not allowed to change contents (add/remove objects) by the guest. The restriction is set by the host and enforced by the mc hardware. The DPAA2 objects can be directly assigned to the guest. However the MC portals (the memory mapped command interface to the MC) need to be emulated because there are commands that configure the interrupts and the isolation IDs which are virtual in the guest. Example: echo vfio-fsl-mc > /sys/bus/fsl-mc/devices/dprc.2/driver_override echo dprc.2 > /sys/bus/fsl-mc/drivers/vfio-fsl-mc/bind The dprc.2 is bound to the VFIO driver and all the objects within dprc.2 are going to be bound to the VFIO driver. More details about the DPAA2 objects can be found here: Documentation/networking/device_drivers/freescale/dpaa2/overview.rst The patches are dependent on some changes in the mc-bus (bus/fsl-mc) driver. The changes were needed in order to re-use code and to export some more functions that are needed by the VFIO driver. Currenlty the mc-bus patches are under review: https://www.spinics.net/lists/kernel/msg3680670.html v4 --> v5 - do not allow mmap for DPRCs - style fixes v3 --> v4 - use bus provided functions to tear down the DPRC - added reset support v2 --> v3 - There is no need to align region size to page size - read/write implemented for all DPAA2 objects - review fixes v1 --> v2 - Fixed the container reset, a new flag added to the firmware command - Implement a bus notifier for setting driver_override Bharat Bhushan (1): vfio/fsl-mc: Add VFIO framework skeleton for fsl-mc devices Diana Craciun (9): vfio/fsl-mc: Scan DPRC objects on vfio-fsl-mc driver bind vfio/fsl-mc: Implement VFIO_DEVICE_GET_INFO ioctl vfio/fsl-mc: Implement VFIO_DEVICE_GET_REGION_INFO ioctl call vfio/fsl-mc: Allow userspace to MMAP fsl-mc device MMIO regions vfio/fsl-mc: Added lock support in preparation for interrupt handling vfio/fsl-mc: Add irq infrastructure for fsl-mc devices vfio/fsl-mc: trigger an interrupt via eventfd vfio/fsl-mc: Add read/write support for fsl-mc devices vfio/fsl-mc: Add support for device reset MAINTAINERS | 6 + drivers/vfio/Kconfig | 1 + drivers/vfio/Makefile | 1 + drivers/vfio/fsl-mc/Kconfig | 9 + drivers/vfio/fsl-mc/Makefile | 4 + drivers/vfio/fsl-mc/vfio_fsl_mc.c | 677 ++++++++++++++++++++++ drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c | 193 ++++++ drivers/vfio/fsl-mc/vfio_fsl_mc_private.h | 55 ++ include/uapi/linux/vfio.h | 1 + 9 files changed, 947 insertions(+) create mode 100644 drivers/vfio/fsl-mc/Kconfig create mode 100644 drivers/vfio/fsl-mc/Makefile create mode 100644 drivers/vfio/fsl-mc/vfio_fsl_mc.c create mode 100644 drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c create mode 100644 drivers/vfio/fsl-mc/vfio_fsl_mc_private.h -- 2.17.1