Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp3907538iog; Tue, 28 Jun 2022 05:22:56 -0700 (PDT) X-Google-Smtp-Source: AGRyM1uCQwzP5I+eT75ZWIP4CrqzA3H24Ke7tVLPSfe1xQoCDaNTto2jAAxuzcaPTZngKqmsfn54 X-Received: by 2002:a05:6402:170b:b0:435:5d22:7cd7 with SMTP id y11-20020a056402170b00b004355d227cd7mr23216693edu.383.1656418976484; Tue, 28 Jun 2022 05:22:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656418976; cv=none; d=google.com; s=arc-20160816; b=X/DW+WYClx65xPU+iNSOEnbpWqQgS5cXqgLopK6mwndnJBRflUfo5CDZ3j587tQpgE WMGUz2N5LifGHNPOd9YXgYA/hfNjrGuKs/7gQtyY4ge/rBaZKTeAx2Gl9ooxmlgzR1GT zWtknQZ9xrB1yzEH5p0ZW2H2efHNQaDUoMDwfFI61w2oRQNiB+Z7ub1Lo8mhk54qdKLG rMt9w1QDInAEsHVkCF69fnnL+g7HMyFbLdjC+pcf2xpdt5Uv4WaSoNSN2ukMKO+i3T3L BH0QU+73PgR9E0TzyiLQ9jbtMFJG1c0gMaesYjeniiztLutv7TVSaOt81/RksqBkQD5l AB9Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version:dkim-signature; bh=ddZauxgs0hwCqpk1Kk2l3rlfcajsKYSuQmpLDJpa4rk=; b=b/7TXQ3T4c/DlWA34yX5wOCNzuZX61sXkZqvll8LDyMg50ADOs2TZN1R6IPMbXxShS H5ioSDpY/kMCeEN4UXfKFIreFzJWhiVkvXu8BjVHWM2jDuOlKPwaFyIm9Q6BliqWB6pU 2eBhD+kIeqEBebg4+oyOyljSuTvd8IPa8icCFshNWnROb1gdNwLXY35bLmsaKLoqwq9x lXOuX6T5HiiCIQpAMdAvK9XYyvsPtTL7zAbRLt9+C+wnVNUpFuDx4q/V8iR6ga+5deT9 MOl/s0iRBgdohS/GhSJioSAMeVU2mrq5Wv0TcRsMvKo3KO1QJt3uDRtXDiBhlkrElaUs lRJw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=dvWI+JpX; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id y9-20020a056402270900b0043763a95ce9si14416600edd.458.2022.06.28.05.22.20; Tue, 28 Jun 2022 05:22:56 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@redhat.com header.s=mimecast20190719 header.b=dvWI+JpX; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=redhat.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1345129AbiF1MPq (ORCPT + 99 others); Tue, 28 Jun 2022 08:15:46 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45480 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235331AbiF1MPp (ORCPT ); Tue, 28 Jun 2022 08:15:45 -0400 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 5C8AF23BCA for ; Tue, 28 Jun 2022 05:15:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1656418540; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: in-reply-to:in-reply-to:references:references; bh=ddZauxgs0hwCqpk1Kk2l3rlfcajsKYSuQmpLDJpa4rk=; b=dvWI+JpX0ZCbeHWMGiuzgsKabxlmw69FO67vIHgY0yVX3PqYuX77N8EwwnVHSPPlmqcMCI mFrpMrWXFJDiuv2tzQtEfj3ZVMjpopiv3X7HVYj+A4gNr+fDNt7nODw9SyZE47IjehyHq6 P/A+5urjz/aCcUFgwCGGMN51x8CFiMM= Received: from mail-ed1-f70.google.com (mail-ed1-f70.google.com [209.85.208.70]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id us-mta-529-8HanAEZrNMaO98ntCCnypg-1; Tue, 28 Jun 2022 08:15:39 -0400 X-MC-Unique: 8HanAEZrNMaO98ntCCnypg-1 Received: by mail-ed1-f70.google.com with SMTP id h16-20020a05640250d000b00435bab1a7b4so9475334edb.10 for ; Tue, 28 Jun 2022 05:15:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ddZauxgs0hwCqpk1Kk2l3rlfcajsKYSuQmpLDJpa4rk=; b=bvlD6QVm7SRJqcw1VBZ2YHgxCuWiptIqrAwnkdR+YUKxrF+lBXxWuzkqeIQCOC9iil GLyid+nZeZWg/r1+uyAQjLXA6fdaAtoLBP7kBP2yUSamtbdOvCdqs8KU5WvlMlJVpVNf k6OFxE+7YId5YlB7FWN7IdHs0WHEcFPzlJuVXc6kegIniAkGrHri007qYktnPKgeK2V3 8kDb4CkWv19kCR+bVcoIJcYNN71+2Yz4pJp4oB61QpXFaXSFKGR5kGNHgUBs8RZSrB7T W/YUea3+U5TEzizpX2qXpzeJltCYbaq18x7lc3KZXL8P6rUT2Jems8pC7BLpOdnB/hFi v6ng== X-Gm-Message-State: AJIora+OHkifcK5rjuu3/CmuHh1nxu3mEBgmp5Vp1iLvam8ES4ioCpww vLRzTY7YpAEqTeg7NGw5XCzpvHTfvLfLI7yc7DQvodJ6Pd+inQ1C8IJH357Q2eBpANEI23r0beM QlEI8jOWjJV8aa/a+nNUtJkIJZ+o/YKaDWqAtXUdv X-Received: by 2002:a17:907:60cb:b0:726:a69a:c7a with SMTP id hv11-20020a17090760cb00b00726a69a0c7amr9963933ejc.156.1656418537765; Tue, 28 Jun 2022 05:15:37 -0700 (PDT) X-Received: by 2002:a17:907:60cb:b0:726:a69a:c7a with SMTP id hv11-20020a17090760cb00b00726a69a0c7amr9963920ejc.156.1656418537572; Tue, 28 Jun 2022 05:15:37 -0700 (PDT) MIME-Version: 1.0 References: <20220627083652.880303-1-giovanni.cabiddu@intel.com> In-Reply-To: <20220627083652.880303-1-giovanni.cabiddu@intel.com> From: Vlad Dronov Date: Tue, 28 Jun 2022 14:15:26 +0200 Message-ID: Subject: Re: [PATCH v2 0/4] crypto: qat - enable configuration for 4xxx To: Giovanni Cabiddu Cc: Herbert Xu , linux-crypto@vger.kernel.org, qat-linux@intel.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-3.2 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_LOW, SPF_HELO_NONE,SPF_NONE,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi, On Mon, Jun 27, 2022 at 10:37 AM Giovanni Cabiddu wrote: > > qat_4xxx devices can be configured to allow either crypto or compression > operations. By default, devices are configured statically according > to following rule: > - odd numbered devices assigned to compression services > - even numbered devices assigned to crypto services > > This set exposes two attributes in sysfs that allow to report and change > the state and the configuration of a QAT 4xxx device. > The first, /sys/bus/pci/devices//qat/state, allows to bring a > device down in order to change the configuration, and bring it up again. > The second, /sys/bus/pci/devices//qat/cfg_services, allows to > inspect the current configuration of a device (i.e. crypto or > compression) and change it. > > # cat /sys/bus/pci/devices//qat/state > up > # cat /sys/bus/pci/devices//qat/cfg_services > sym;asym > # echo down > /sys/bus/pci/devices//qat/state > # echo dc > /sys/bus/pci/devices//qat/cfg_services > # echo up > /sys/bus/pci/devices//qat/state > # cat /sys/bus/pci/devices//qat/state > dc > > Changes from v1: > - Updated target kernel version in documentation (from 5.19 to 5.20). > - Fixed commit message in patch #1 and updated documentation in patch > #4 after review from Vladis Dronov. > > Giovanni Cabiddu (4): > crypto: qat - expose device state through sysfs for 4xxx > crypto: qat - change behaviour of adf_cfg_add_key_value_param() > crypto: qat - relocate and rename adf_sriov_prepare_restart() > crypto: qat - expose device config through sysfs for 4xxx The patchset looks good to me. Please feel free to use: Reviewed-by: Vladis Dronov Best regards, Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer