From nobody Mon Apr 15 18:32:11 2024 X-Original-To: wireless@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4VJG4h1Hmhz5H6CT for ; Mon, 15 Apr 2024 18:32:52 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Received: from mail-lf1-f42.google.com (mail-lf1-f42.google.com [209.85.167.42]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (2048 bits) client-digest SHA256) (Client CN "smtp.gmail.com", Issuer "GTS CA 1D4" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4VJG4g0Vnsz4KM2 for ; Mon, 15 Apr 2024 18:32:51 +0000 (UTC) (envelope-from ccfreebsd@gmail.com) Authentication-Results: mx1.freebsd.org; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=freebsd.org (policy=none); spf=pass (mx1.freebsd.org: domain of ccfreebsd@gmail.com designates 209.85.167.42 as permitted sender) smtp.mailfrom=ccfreebsd@gmail.com Received: by mail-lf1-f42.google.com with SMTP id 2adb3069b0e04-518d98b9620so1845512e87.3 for ; Mon, 15 Apr 2024 11:32:51 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713205968; x=1713810768; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=g9ZKBwEYw1C9uKUlUU1TznK9Ux45yNPEzjIflfWpcFY=; b=qlxDEFTLtcP+iPNhZTP5dFCxDsw2SE0Lh5FKdJOuEPvCfTkmNU9Rx6rpS9rENSxoKR Uo5GIfurSCnpjxYvFUS5MYeui0nVcveegDkVqBLQG1qgmYwdF0UwwbqS2R8FdEdgFWxU +yjCp3PRKp9IcCO3dwuYabyf7ptf2RdpcAEPxV4O7POzwLZz+SKNq+eQJ9kEZpOmU1cZ 5l8CrsPxJVxCp/WNfFk/K+PtDsWAaYvuXjOkK7rsB63c1tMkl9FsnJ+doX8sm3WtBqdw YmPfxxYFAHBLy2KQZnil3bNvYSs5xvB8HBfc0VrgNODcmxE5TUPRUc3Nv+RO57tD/bp4 dusw== X-Gm-Message-State: AOJu0YzWZJGClLUxnWWYE7Q1CBCmqSOrOHso7BzlMd/drhheBieB4hC1 u1vJ/7rqn0hdy9F+2ZSWL2nbQ4r6Xu8AW6ytXHtL9SDsZBq225ruSfAVKGs3 X-Google-Smtp-Source: AGHT+IGsm+96gYXk+VG5Z98yyVg5r0kMJ/VY8YGdtR5ULk9uE5ywmra02M5/2ut43086qiVWXlUPzA== X-Received: by 2002:a05:6512:98f:b0:516:cd83:a96a with SMTP id w15-20020a056512098f00b00516cd83a96amr6335817lft.37.1713205968188; Mon, 15 Apr 2024 11:32:48 -0700 (PDT) Received: from mail-lf1-f47.google.com (mail-lf1-f47.google.com. [209.85.167.47]) by smtp.gmail.com with ESMTPSA id i5-20020a198c45000000b00516cef1f1casm1357783lfj.181.2024.04.15.11.32.48 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 15 Apr 2024 11:32:48 -0700 (PDT) Received: by mail-lf1-f47.google.com with SMTP id 2adb3069b0e04-516d487659bso4285191e87.2 for ; Mon, 15 Apr 2024 11:32:48 -0700 (PDT) X-Received: by 2002:a2e:9e87:0:b0:2d8:a889:172 with SMTP id f7-20020a2e9e87000000b002d8a8890172mr5999541ljk.8.1713205967898; Mon, 15 Apr 2024 11:32:47 -0700 (PDT) List-Id: Discussions List-Archive: https://lists.freebsd.org/archives/freebsd-wireless List-Help: List-Post: List-Subscribe: List-Unsubscribe: X-BeenThere: freebsd-wireless@freebsd.org Sender: owner-freebsd-wireless@FreeBSD.org MIME-Version: 1.0 From: Cheng Cui Date: Mon, 15 Apr 2024 14:32:11 -0400 X-Gmail-Original-Message-ID: Message-ID: Subject: Weekly Development report(Apr 08 ~ Apr 12) on the iwlwifi WiFi project To: wireless@freebsd.org Content-Type: multipart/alternative; boundary="00000000000024dd84061626d9fa" X-Spamd-Bar: -- X-Spamd-Result: default: False [-2.78 / 15.00]; NEURAL_HAM_LONG(-1.00)[-1.000]; NEURAL_HAM_MEDIUM(-1.00)[-1.000]; NEURAL_HAM_SHORT(-0.88)[-0.876]; FORGED_SENDER(0.30)[cc@freebsd.org,ccfreebsd@gmail.com]; R_SPF_ALLOW(-0.20)[+ip4:209.85.128.0/17:c]; MIME_GOOD(-0.10)[multipart/alternative,text/plain]; DMARC_POLICY_SOFTFAIL(0.10)[freebsd.org : SPF not aligned (relaxed), No valid DKIM,none]; FROM_HAS_DN(0.00)[]; TO_MATCH_ENVRCPT_ALL(0.00)[]; RCVD_TLS_LAST(0.00)[]; RCVD_COUNT_THREE(0.00)[3]; ARC_NA(0.00)[]; RCPT_COUNT_ONE(0.00)[1]; MIME_TRACE(0.00)[0:+,1:+,2:~]; MISSING_XM_UA(0.00)[]; RCVD_VIA_SMTP_AUTH(0.00)[]; FREEMAIL_ENVFROM(0.00)[gmail.com]; PREVIOUSLY_DELIVERED(0.00)[wireless@freebsd.org]; TO_DN_NONE(0.00)[]; FROM_NEQ_ENVFROM(0.00)[cc@freebsd.org,ccfreebsd@gmail.com]; ASN(0.00)[asn:15169, ipnet:209.85.128.0/17, country:US]; MLMMJ_DEST(0.00)[wireless@freebsd.org]; TO_DOM_EQ_FROM_DOM(0.00)[]; R_DKIM_NA(0.00)[]; RWL_MAILSPIKE_POSSIBLE(0.00)[209.85.167.42:from]; RCVD_IN_DNSWL_NONE(0.00)[209.85.167.47:received,209.85.167.42:from] X-Rspamd-Queue-Id: 4VJG4g0Vnsz4KM2 --00000000000024dd84061626d9fa Content-Type: text/plain; charset="UTF-8" Still working on the HW key/encryption/decryption support under the `LKPI_80211_HW_CRYPTO` block. - This week I was mainly testing different ideas and digging up different code paths to see any clue that leads to HW crypto offload malfunction. 1. Firstly, I figured out how to reproduce the malfunction in Linux kernel, with the way to nullify info->control.hw_key right before iwl_mvm_set_tx_params() inside iwl_mvm_tx_mpdu(). I added this info in the tracking PR 277996 . 2. We(adrian@ bz@ and me) are in sync with the issue. Adrian is very kind and introduced some related work background. 3. So far, some missing flags, e.g. IEEE80211_KEY_FLAG_PAIRWISE or ieee80211_tx_info_flags do not help. And my blind guess of shrinking ieee80211_tx_info size to match Linux skb->cb 48 Byte size does not seem to work either. Will again dig up the driver hw key setup path in Linux and investigate. -- Best Regards, Cheng Cui --00000000000024dd84061626d9fa Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Still working on the HW key/encryption/decryption support = under the `LKPI_80211_HW_CRYPTO` block.

  • This wee= k I was mainly testing different ideas and digging up different=C2=A0code p= aths to see any clue that leads to HW crypto offload malfunction.
    • <= /ul>
      1. Firstly, I figured out how to reproduce the malfunction in = Linux kernel, with the way to=C2=A0nullify info->control.hw_key right be= fore iwl_mvm_set_tx_params() inside iwl_mvm_tx_mpdu(). I added this info in= the tracking PR=C2=A0277996.
      2. We(adrian@ bz@ and = me) are in sync with the issue. Adrian is very kind and introduced some rel= ated work background.
      3. So far, some missing flags, e.g.=C2=A0IEEE802= 11_KEY_FLAG_PAIRWISE or=C2=A0ieee80211_tx_info_flags do not help. And my bl= ind guess of shrinking=C2=A0ieee80211_tx_info size to match Linux skb->c= b 48 Byte=C2=A0size does not seem to work either.
    Will again = dig up the driver hw key setup path in Linux and investigate.

    <= /div>--
    Best Regards,
    Cheng Cui
--00000000000024dd84061626d9fa--