From patchwork Tue Sep 3 03:52:56 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Zhangfei Gao X-Patchwork-Id: 172767 Delivered-To: patch@linaro.org Received: by 2002:a92:d204:0:0:0:0:0 with SMTP id y4csp5104252ily; Mon, 2 Sep 2019 20:55:04 -0700 (PDT) X-Google-Smtp-Source: APXvYqyRNTEYmAvBBo9gozpUIp6J99b5NX1XjBxoMFMcYgNS2fQCkTAce2Ro0HeLGt/NYCdGl6V1 X-Received: by 2002:a17:902:7687:: with SMTP id m7mr1507929pll.41.1567482904745; Mon, 02 Sep 2019 20:55:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567482904; cv=none; d=google.com; s=arc-20160816; b=BBDxGcU1v3cFcrD2aDfsOsDGJr4ucT4IQ7XEA/ACiZjhV/TMqgSGnRl3WAu7eNz3Fe aNq5SK2sJsfd3mmsAQKcha/OEdJwwdjB3TmTzXxlRrH7DPZYZfLmw1WiioQmpR1IrGeN Xuvt4e8t86A/iR3UBnEV3AkinIulN+8JduadQBYcYQwwCUNGqRj7XgIpQiVkEGH1mL2w HzmthaJw9MasRW2ltX5P4jpabwtvVs2Si4rrPOQjopJ6+TAaH6HiaLsgeXWrN/HSiwXy aeDcRzipUIXGaaeqzEocQ3LAN8iQAwqORysMAtR/0VBBZ/NdJFIr6IZj7R/aAT6zonxp DWoA== 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 :dkim-signature; bh=L/Ylww4xlUThxeTDdjn9aGKgbvbOPz27jtSswl52ZqI=; b=AA7TtVwhHKhFEettdU6S1UPb4FgX4ihxYjBwuBeh3VUZJanzk0bqbl9k2z8HOlpTyU rjjYMb/4gA7D8oO/NTjGQR3dsElO/MdXxTTDUdx31uwKICpeTN8Jf1PNwn2X3FFEQaxW zvlTaHk33iuhD2lAsVccdxk7F1eRIvA7Cfy7YRnHa/qaejJ9oOYIN2EGZgjOHCyiRInQ iX79hJbS7iqW8JdZEiVQ0eZadTNqxdTtYFp1D5/Ne305ZpEXtGzM6r1F/5MpMoKmznEd a9fVzSgtWFaD2MRM5TKAhj4BPb3ffjN7U1mxPsDv1pzfQL7lcA6EKKf11MtLCOHOPDkJ v42w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=syOytE7Z; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s61si13365796plb.102.2019.09.02.20.55.04; Mon, 02 Sep 2019 20:55:04 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=syOytE7Z; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726267AbfICDzD (ORCPT + 28 others); Mon, 2 Sep 2019 23:55:03 -0400 Received: from mail-pg1-f195.google.com ([209.85.215.195]:38530 "EHLO mail-pg1-f195.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725821AbfICDzD (ORCPT ); Mon, 2 Sep 2019 23:55:03 -0400 Received: by mail-pg1-f195.google.com with SMTP id d10so3792744pgo.5 for ; Mon, 02 Sep 2019 20:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=from:to:cc:subject:date:message-id; bh=L/Ylww4xlUThxeTDdjn9aGKgbvbOPz27jtSswl52ZqI=; b=syOytE7Z9tJHwn1wsEtJ+hWykOXtCwEqInp70AFKkSJnDD8cu3UoXeRNpzzTjjh0Yk Uu3HeK+xXmdb6gBc/tjxHDIM5KAB4ioB4hiVRLcsg4SwVe+00ylaE7Bn0GVlsBICme7p TX87GJUTwtm5zT4JUt7hdIbEieCOvGRt3vJWLiAnmGDATcreCTVJA9xVbx7oVJxnz3ny HoozRHqBQ/KC5Q64ZDiXftawkJoyeaDxMOB9zPfwAeMwTc/Caje0JhR+h2HtJjJpupqg oMfudjhENWIvp0agkl62UOqU4YEtl9ovP2vKLpUfWedTOTM7cMqnPTaNfwA8DvEL+5l2 NQnA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id; bh=L/Ylww4xlUThxeTDdjn9aGKgbvbOPz27jtSswl52ZqI=; b=exTWBPZF/oneSwl59QrwsMjltQNyNOyUJaIV3Mu2ZNqfdtJCmHGV9NMe9aU5bcIYHE 992sfh56FAuZ7fy8ptbE6f9R+8ztI0MwVFMRCkTWyuAWFiygIYPUBRP6JMI3mxv7TaQP 5/Xqs6EPslJwLc1TUi7pQNk3Q9xTGmWlsV2wmPboSyRD0DW6xyP9SCMgnvcXYow85DN9 DeayahQm6p8xqYguyVRe1oKzJywHnO4EO5yGOT6S0bORU3ohc/UeufQ0YK99GcSyhmOU WS4Xfa6d/kun7kVogB+fG4oSaqL4MUthy0xpEWm5fU9/J2h7w8628KHM9cDfonVM7FhM mk0A== X-Gm-Message-State: APjAAAX54ISD3Mbdj/W9to09MlaRbYh4wMJAxnFgS4dcFPqL8mXy7kgc l4/JfUPvet1vjxq0ZKIZET69TQ== X-Received: by 2002:aa7:9117:: with SMTP id 23mr14656447pfh.94.1567482902071; Mon, 02 Sep 2019 20:55:02 -0700 (PDT) Received: from localhost.localdomain ([240e:362:47f:ba00:a424:c9b7:932a:4fc2]) by smtp.gmail.com with ESMTPSA id j7sm6826356pfi.96.2019.09.02.20.53.44 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Mon, 02 Sep 2019 20:55:01 -0700 (PDT) From: Zhangfei Gao To: Greg Kroah-Hartman , Arnd Bergmann , jonathan.cameron@huawei.com, kenneth-lee-2012@foxmail.com, Wangzhou Cc: linux-accelerators@lists.ozlabs.org, linux-kernel@vger.kernel.org, Zhangfei Gao Subject: [PATCH v3 0/2] Add uacce module for Accelerator Date: Tue, 3 Sep 2019 11:52:56 +0800 Message-Id: <1567482778-5700-1-git-send-email-zhangfei.gao@linaro.org> X-Mailer: git-send-email 2.7.4 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Uacce (Unified/User-space-access-intended Accelerator Framework) targets to provide Shared Virtual Addressing (SVA) between accelerators and processes. So accelerator can access any data structure of the main cpu. This differs from the data sharing between cpu and io device, which share data content rather than address. Because of unified address, hardware and user space of process can share the same virtual address in the communication. Uacce is intended to be used with Jean Philippe Brucker's SVA patchset[1], which enables IO side page fault and PASID support. We have keep verifying with Jean's sva/current [2] We also keep verifying with Eric's SMMUv3 Nested Stage patch [3] This series and related zip & qm driver https://github.com/Linaro/linux-kernel-warpdrive/tree/5.3-rc1-warpdrive-v3 The library and user application: https://github.com/Linaro/warpdrive/tree/wdprd-v1-upstream References: [1] http://jpbrucker.net/sva/ [2] http://www.linux-arm.org/git?p=linux-jpb.git;a=shortlog;h=refs/heads/sva/current [3] https://github.com/eauger/linux/tree/v5.3.0-rc0-2stage-v9 Change History: v3: Recommended by Greg, use sturct uacce_device instead of struct uacce, and use struct *cdev in struct uacce_device, as a result, cdev can be released by itself when refcount decreased to 0. So the two structures are decoupled and self-maintained by themsleves. Also add dev.release for put_device. v2: Address comments from Greg and Jonathan Modify interface uacce_register Drop noiommu mode first v1: 1. Rebase to 5.3-rc1 2. Build on iommu interface 3. Verifying with Jean's sva and Eric's nested mode iommu. 4. User library has developed a lot: support zlib, openssl etc. 5. Move to misc first RFC3: https://lkml.org/lkml/2018/11/12/1951 RFC2: https://lwn.net/Articles/763990/ Background of why Uacce: Von Neumann processor is not good at general data manipulation. It is designed for control-bound rather than data-bound application. The latter need less control path facility and more/specific ALUs. So there are more and more heterogeneous processors, such as encryption/decryption accelerators, TPUs, or EDGE (Explicated Data Graph Execution) processors, introduced to gain better performance or power efficiency for particular applications these days. There are generally two ways to make use of these heterogeneous processors: The first is to make them co-processors, just like FPU. This is good for some application but it has its own cons: It changes the ISA set permanently. You must save all state elements when the process is switched out. But most data-bound processors have a huge set of state elements. It makes the kernel scheduler more complex. The second is Accelerator. It is taken as a IO device from the CPU's point of view (but it need not to be physically). The process, running on CPU, hold a context of the accelerator and send instructions to it as if it calls a function or thread running with FPU. The context is bound with the processor itself. So the state elements remain in the hardware context until the context is released. We believe this is the core feature of an "Accelerator" vs. Co-processor or other heterogeneous processors. The intention of Uacce is to provide the basic facility to backup this scenario. Its first step is to make sure the accelerator and process can share the same address space. So the accelerator ISA can directly address any data structure of the main CPU. This differs from the data sharing between CPU and IO device, which share data content rather than address. So it is different comparing to the other DMA libraries. In the future, we may add more facility to support linking accelerator library to the main application, or managing the accelerator context as special thread. But no matter how, this can be a solid start point for new processor to be used as an "accelerator" as this is the essential requirement. Kenneth Lee (2): uacce: Add documents for uacce uacce: add uacce driver Documentation/ABI/testing/sysfs-driver-uacce | 47 ++ Documentation/misc-devices/uacce.rst | 309 ++++++++ drivers/misc/Kconfig | 1 + drivers/misc/Makefile | 1 + drivers/misc/uacce/Kconfig | 13 + drivers/misc/uacce/Makefile | 2 + drivers/misc/uacce/uacce.c | 1094 ++++++++++++++++++++++++++ include/linux/uacce.h | 172 ++++ include/uapi/misc/uacce.h | 39 + 9 files changed, 1678 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-driver-uacce create mode 100644 Documentation/misc-devices/uacce.rst create mode 100644 drivers/misc/uacce/Kconfig create mode 100644 drivers/misc/uacce/Makefile create mode 100644 drivers/misc/uacce/uacce.c create mode 100644 include/linux/uacce.h create mode 100644 include/uapi/misc/uacce.h -- 2.7.4