Received: by 2002:a05:6902:102b:0:0:0:0 with SMTP id x11csp262981ybt; Mon, 6 Jul 2020 08:45:05 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwymGn6sHWfzllb9yS+oLeZRRmTFmpVylQvSv3BRWWJSossUtvoNIh2Lytn4u4w8emLDoET X-Received: by 2002:a17:906:2b50:: with SMTP id b16mr45798299ejg.410.1594050304943; Mon, 06 Jul 2020 08:45:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1594050304; cv=none; d=google.com; s=arc-20160816; b=jX6D/Kt/eLNQS7ullgE8EiqQ+GInjWoJUWjKHtQEofotrYIek/nzSI60VayRRYZgVO RnVGzffqyMGVBLAzVdkbHwkMhOQ73uCO7fBMBt7cLTBT92utjWC8AySAmvJfjqWHLtNC YNbhLIQNv0XSYUrS4nWMxNju/fSEguA4u29ajUuoQf10BtcMLQQcVqBkuD3ON1XXgT57 tFtq2MnXHotqeAenr4izbELFd5ACThotZFohSUKCyYQiKrZ2oJbcBIRLYz39jdRw7VXw 7/v0Y7RaWKNsU/5oXMyFPnQpzMb2NtTifkbfo4TBHTJrDoyPUOYbTvktXXZbJQpIyYGG Q4KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:date:subject:cc:to:from; bh=U7kA6Vf0p7zSxa/8MKkveGs6DlSByOQ9V1cxwBI8Si0=; b=a5wAcpPCTGXCfIRxN9AD7QYG4GAwcLT3FJFgbnCp7IoBGQlSaxxYy+TZHiQCNDsq58 dRzYiOoCKX14bbBLgGUAEWbDRw7i35nER4bpHsriN4m1/w4Qv79i516J3n8JyP7JK+ii BjcaMY8T83tWjKlIMThIOkTrP03x3KppkyphgqXB1U7W5F4xdUhPE9a5iCKXK5VOpc8d OEJ4gZhWJbIvpPRMiqhPmdaSQAnveUUAGbbV0aZyIdBhdcxgHr7fSrRYftv5xHLSB1BK SXhFSdIQ89tu0x3IsVUb83gMobwi8Pnru73dxdeLVwk+PVkub5kSZTQxl6mezpscKtJS Apng== 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 b13si6185957edz.152.2020.07.06.08.44.42; Mon, 06 Jul 2020 08:45:04 -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 S1729412AbgGFPmO (ORCPT + 99 others); Mon, 6 Jul 2020 11:42:14 -0400 Received: from inva020.nxp.com ([92.121.34.13]:46440 "EHLO inva020.nxp.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729197AbgGFPmO (ORCPT ); Mon, 6 Jul 2020 11:42:14 -0400 Received: from inva020.nxp.com (localhost [127.0.0.1]) by inva020.eu-rdc02.nxp.com (Postfix) with ESMTP id 4BC651A072D; Mon, 6 Jul 2020 17:42:12 +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 3C1921A072C; Mon, 6 Jul 2020 17:42:12 +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 E8F8C203C3; Mon, 6 Jul 2020 17:42:11 +0200 (CEST) From: Diana Craciun To: alex.williamson@redhat.com, kvm@vger.kernel.org Cc: bharatb.linux@gmail.com, linux-kernel@vger.kernel.org, laurentiu.tudor@nxp.com, Diana Craciun Subject: [PATCH v3 0/9] vfio/fsl-mc: VFIO support for FSL-MC devices Date: Mon, 6 Jul 2020 18:41:44 +0300 Message-Id: <20200706154153.11477-1-diana.craciun@oss.nxp.com> X-Mailer: git-send-email 2.17.1 X-Virus-Scanned: ClamAV using ClamSMTP Sender: linux-kernel-owner@vger.kernel.org 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/msg3578910.html 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 (8): 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 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 | 687 ++++++++++++++++++++++ drivers/vfio/fsl-mc/vfio_fsl_mc_intr.c | 221 +++++++ drivers/vfio/fsl-mc/vfio_fsl_mc_private.h | 55 ++ include/uapi/linux/vfio.h | 1 + 9 files changed, 985 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