From patchwork Thu Dec 29 18:22:36 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Cristian Marussi X-Patchwork-Id: 13083673 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 70E19C4332F for ; Thu, 29 Dec 2022 18:34:01 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Message-Id:Date:Subject:Cc :To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References: List-Owner; bh=M2T46NF0Ui7VsoNhaYUim+MLB0xB8PlevJEJfFcL04g=; b=cTBla3Pk1SK033 zXGGjPtqFe60/f8ejCbNQWqGZa4EbNs7W34De/nMXpXu8Naa3IgPwFuSbmcBAqxxI7JfZXCeSCvz9 w5JzLTq3BoI1RZK3ycBn+O00bcPSFJJ5NABiqHQL/xwy+lCgxm5lPhU2PBwCS6GA1IcQi9eBWhMFt 1w/D3bqeHD2XjSNPi33/oYBSLah2FHrKgAM/FM3Unmkyf9qALSRptylJG5fXxJ/Zmj20BGy5FtICz Z8oqk2g2mQM24H5rSK4vRctOJM3lAK250jSZT8Qqrp53kuPyRz5K4pQ73+29qRRFhn16Mt4anuxcg d2YAy51DUUE9+Y8e0jLw==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pAxhz-000p8R-Pr; Thu, 29 Dec 2022 18:32:51 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1pAxZb-000kZ3-20 for linux-arm-kernel@lists.infradead.org; Thu, 29 Dec 2022 18:24:14 +0000 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 068EE2F4; Thu, 29 Dec 2022 10:24:31 -0800 (PST) Received: from e120937-lin.. (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 7274A3F71A; Thu, 29 Dec 2022 10:23:47 -0800 (PST) From: Cristian Marussi To: linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Cc: sudeep.holla@arm.com, james.quinlan@broadcom.com, Jonathan.Cameron@Huawei.com, f.fainelli@gmail.com, etienne.carriere@linaro.org, vincent.guittot@linaro.org, souvik.chakravarty@arm.com, wleavitt@marvell.com, peter.hilber@opensynergy.com, nicola.mazzucato@arm.com, tarek.el-sherbiny@arm.com, quic_kshivnan@quicinc.com, cristian.marussi@arm.com Subject: [PATCH v6 00/17] Introduce a unified API for SCMI Server testing Date: Thu, 29 Dec 2022 18:22:36 +0000 Message-Id: <20221229182253.948175-1-cristian.marussi@arm.com> X-Mailer: git-send-email 2.34.1 MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20221229_102411_337026_83E48CF0 X-CRM114-Status: GOOD ( 38.30 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hi all, This series aims to introduce a new SCMI unified userspace interface meant to ease testing an SCMI Server implementation for compliance, fuzzing etc., from the perspective of the OSPM agent (non-secure world only ...) It is proposed as a testing/development facility, it is NOT meant to be a feature to use in production, but only enabled in Kconfig for test deployments. Currently an SCMI Compliance Suite like the one at [1] can only work by injecting SCMI messages at the SCMI transport layer using the mailbox test driver (CONFIG_MAILBOX_TEST) via its few debugfs entries and looking at the related replies from the SCMI backend Server. This approach has a few drawbacks: - the SCMI Server under test MUST be reachable through a mailbox based SCMI transport: any other SCMI Server placement is not possible (like in a VM reachable via SCMI Virtio). In order to cover other placements in the current scenario we should write some sort of test driver for each and every existent SCMI transport and for any future additional transport ...this clearly does not scale. - even in the mailbox case the userspace Compliance suite cannot simply send and receive bare SCMI messages BUT it has to properly lay them out into the shared memory exposed by the mailbox test driver as expected by the transport definitions. In other words such a userspace test application has to, not only use a proper transport driver for the system at hand, but it also has to have a comprehensive knowledge of the internals of the underlying transport in order to operate. - last but not least, the system under test has to be specifically configured and built, in terms of Kconfig and DT, to perform such kind of testing, it cannot be used for anything else, which is unfortunate for CI/CD deployments. This series introduces a new SCMI Raw mode support feature that, when configured and enabled exposes a new interface in debugfs through which: - a userspace application can inject bare SCMI binary messages into the SCMI core stack; such messages will be routed by the SCMI regular kernel stack to the backend Server using the currently configured transport transparently: in other words you can test the SCMI server, no matter where it is placed, as long as it is reachable from the currently configured SCMI stack. Same goes the other way around on the reading path: any SCMI server reply can be read as a bare SCMI binary message from the same debugfs path. - as a direct consequence of this way of injecting bare messages in the middle of the SCMI stack (instead of beneath it at the transport layer) the user application has to handle only bare SCMI messages without having to worry about the specific underlying transport internals that will be taken care of by the SCMI core stack itself using its own machinery, without duplicating such logic. - a system under test, once configured with SCMI Raw support enabled in Kconfig, can be booted without any particular DT change. In the last V6: - improved scmi traces for msg dumps to include used channels - added a new common SCMI debugfs root fs - reworked SCMI Raw debugfs layout - added support of a new additional per-channel API that allows a user to select a specific egress channel for the message injection A quick and trivial example from the shell...reading from a sensor injecting a properly crafted packet in raw mode: # INJECT THE SENSOR_READING MESSAGE FOR SENSOR ID=1 (binary little endian) root@deb-buster-arm64:~# echo -e -n \\x06\\x54\\x00\\x00\\x01\\x00\\x00\\x00\\x00\\x00\\x00\\x00 > /sys/kernel/debug/scmi/0/raw/message # READING BACK THE REPLY... root@deb-buster-arm64:~# cat /sys/kernel/debug/scmi/0/raw/message | od --endian=little -t x4 0000000 00005406 00000000 00000335 00000000 0000020 while doing that, since Raw mode makes (partial) use of the regular SCMI stack, you can observe the messages going through the SCMI stack with the usual traces: bash-329 [000] ..... 14183.446808: scmi_msg_dump: id=0 ch=10 pt=15 t=cmnd msg_id=06 seq=0000 s=0 pyld=0100000000000000 irq/35-mhu_db_l-81 [000] ..... 14183.447809: scmi_msg_dump: id=0 ch=10 pt=15 t=resp msg_id=06 seq=0000 s=0 pyld=3503000000000000 ..trying to read in async when the backend server does NOT supports asyncs: # AN ASYNC SENSOR READING REQUEST... root@deb-buster-arm64:~# echo -e -n \\x06\\x54\\x00\\x00\\x01\\x00\\x00\\x00\\x01\\x00\\x00\\x00 > /sys/kernel/debug/scmi/0/raw/message_async bash-329 [000] ..... 16415.938739: scmi_msg_dump: id=0 ch=10 pt=15 t=cmnd msg_id=06 seq=0000 s=0 pyld=0100000001000000 irq/35-mhu_db_l-81 [000] ..... 16415.944129: scmi_msg_dump: id=0 ch=10 pt=15 t=resp msg_id=06 seq=0000 s=-1 pyld= # RETURNS A STATUS -1 FROM THE SERVER NOT SUPPORTING IT root@deb-buster-arm64:~# cat /sys/kernel/debug/scmi/0/raw/message | od --endian=little -t x4 0000000 00005406 ffffffff 0000010 Note that the above example was on a JUNO, BUT exactly the same steps can be used to reach an SCMI Server living on a VM reachable via virtio as long as the system under test if properly configured to work with a virtio transport. In a nutshell the exposed API is as follows: /sys/kernel/debug/scmi/ `-- 0 |-- atomic_threshold_us |-- instance_name |-- raw | |-- channels | | |-- 0x10 | | | |-- message | | | `-- message_async | | `-- 0x13 | | |-- message | | `-- message_async | |-- errors | |-- message | |-- message_async | |-- notification | `-- reset `-- transport |-- is_atomic |-- max_msg_size |-- max_rx_timeout_ms |-- rx_max_msg |-- tx_max_msg `-- type ... where at the top level: - : a progressive sequence number identifying this SCMI instance, in case there are multiple SCMI instance defined - instance_name: can be used to identify the SCMI instance that you are using through this Raw accessors: it corresponds to the SCMI DT top node full name of the underlying SCMI instance ... rooted under /transport: - a bunch of configuration info useful to setup the user application expectations in terms of timeouts and message characteristics. ... rooted at /raw (the real SCMI Raw interface :D): - message*: used to send sync/async commands and read back immediate and delayed responses (if any) - errors: used to report timeout and unexpected replies - reset: used to reset the SCMI Raw stack, flushing all queues from received messages still pending to be read out (useful to be sure to cleanup between test suite runs...) - notification: used to read any notification being spit by the system (if previously enabled by the user app) ... rooted at /raw/channels//: - message*: used to send sync/async commands and read back immediate and delayed responses (if any), using a SPECIFIC transport channel (instead of letting the system choose for you based on transport config and the rotocol embedded in the injected message) Note that these entries are optional, created only if there is more than transport channel defined on the system Each write corresponds to one command request and the replies or delayed response are read back one message at time (receiving an EOF at each message boundary). The user application running the test is in charge of handling timeouts and properly choosing SCMI sequence numbers for the outgoing requests: note that the same fixed number can be re-used (...though discouraged...) as long as the suite does NOT expect to send multiple in-flight commands concurrently. Since the SCMI core regular stack is partially used to deliver and collect the messages, late replies after timeouts and any other sort of unexpected message sent by the SCMI server platform back can be identified by the SCMI core as usual and it will be reported under /errors for later analysis. (a userspace test-app will have anyway properly detected the timeout on /message* ...) All of the above has been roughly tested against a standard JUNO SCP SCMI Server (mailbox trans) and an emulated SCMI Server living in a VM (virtio trans) using a custom experimental version of the scmi-tests Compliance suite patched to support Raw mode and posted at [2]. (still in development ...merge requests are in progress...for now it is just a mean for me to test the testing API ... O_o) This V6 series is based on v6.2-rc1 PLUS another series which reworked a bit the SCMI core stack init/probe [3]; to ease testing a V6 properly based can be picked up from [4]. Having said that (in such a concise and brief way :P) ... ...any feedback/comments are welcome ! Thanks, Cristian --- v5 --> v6 - exported symbol debugfs_create_str - rebased on top of v6.2-rc1 plus series at [3] - redesigned SCMI debugfs layout with a bunch of common entries enabled by implicit CONFIG_ARM_SCMI_NEED_DEBUGFS - refactored SCMI Raw internal queues handling - added SCMI Raw per-channel injection support - added channels info on SCMI msg_dump traces - fix debugfs multiple writers cases - added DEBUG_FS dependency to Raw mode - select CONFIG_ARM_SCMI_NEED_DEBUGFS when Raw mode is compiled v4 --> v5 - rebased on sudeep/for-next/scmi - added multiple SCMI instances support - added optional Raw full-cohexistence mode - use custom tags to distinguish Raw msg_dump traces - add circular handling of raw buffers queues for errors and notifications V3 --> v4 - rebased on v6.1-rc1 - addedd missing support for 'polled' transports and transport lacking a completion_irq (like smc/optee) - removed a few inlines - refactored SCMI Raw RX patch to make use more extensively of the regular non-Raw RX path - fix handling of O_NONBLOCK raw_mode read requests v2 --> v3 - fixed some sparse warning on LE and __poll_t - reworked and simplified deferred worker in charge of xfer delayed waiting - allow for injection of DT-unknown protocols messages when in Raw mode (needed for any kind of fuzzing...) v1 --> v2 - added comments and debugfs docs - added dedicated transport devices for channels initialization - better channels handling in Raw mode - removed runtime enable, moved to static compile time exclusion of SCMI regular stack [1]: https://gitlab.arm.com/tests/scmi-tests [2]: https://gitlab.arm.com/tests/scmi-tests/-/commits/raw_mode_support_devel/ [3]: https://lore.kernel.org/all/20221222185049.737625-1-cristian.marussi@arm.com/ [4]: https://gitlab.arm.com/linux-arm/linux-cm/-/commits/scmi_raw_mode_V6/ Cristian Marussi (17): firmware: arm_scmi: Refactor xfer in-flight registration routines firmware: arm_scmi: Refactor polling helpers firmware: arm_scmi: Refactor scmi_wait_for_message_response firmware: arm_scmi: Add flags field to xfer firmware: arm_scmi: Add xfer Raw helpers firmware: arm_scmi: Move errors defs and code to common.h firmware: arm_scmi: Add internal platform/channel IDs include: trace: Add platform and channel instance references debugfs: Export debugfs_create_str symbol firmware: arm_scmi: Populate a common SCMI debugsfs root firmware: arm_scmi: Add debugfs ABI documentation for common entries firmware: arm_scmi: Add core Raw transmission support firmware: arm_scmi: Add debugfs ABI documentation for Raw mode firmware: arm_scmi: Reject SCMI drivers while in Raw mode firmware: arm_scmi: Call Raw mode hooks from the core stack firmware: arm_scmi: Add Raw mode coexistence support firmware: arm_scmi: Add per-channel Raw injection support Documentation/ABI/testing/debugfs-scmi | 70 + Documentation/ABI/testing/debugfs-scmi-raw | 109 ++ drivers/firmware/arm_scmi/Kconfig | 32 + drivers/firmware/arm_scmi/Makefile | 1 + drivers/firmware/arm_scmi/bus.c | 7 + drivers/firmware/arm_scmi/common.h | 73 + drivers/firmware/arm_scmi/driver.c | 638 +++++++-- drivers/firmware/arm_scmi/protocols.h | 7 + drivers/firmware/arm_scmi/raw_mode.c | 1443 ++++++++++++++++++++ drivers/firmware/arm_scmi/raw_mode.h | 31 + fs/debugfs/file.c | 1 + include/trace/events/scmi.h | 18 +- 12 files changed, 2289 insertions(+), 141 deletions(-) create mode 100644 Documentation/ABI/testing/debugfs-scmi create mode 100644 Documentation/ABI/testing/debugfs-scmi-raw create mode 100644 drivers/firmware/arm_scmi/raw_mode.c create mode 100644 drivers/firmware/arm_scmi/raw_mode.h