Re: [Intel-wired-lan] [iwl-next v7 8/9] ice: simplify VF MSI-X managing

2024-11-13 Thread Romanowski, Rafal
> -Original Message- > From: Intel-wired-lan On Behalf Of Michal > Swiatkowski > Sent: Monday, November 4, 2024 1:14 PM > To: intel-wired-...@lists.osuosl.org > Cc: pmen...@molgen.mpg.de; Drewek, Wojciech ; > Szycik, Marcin ; net...@vger.kernel.org; Knitter, > Konrad ; Chmielewski, Pawel >

[Intel-wired-lan] [PATCH iwl-net 01/10] idpf: initial PTP support

2024-11-13 Thread Milena Olech
PTP feature is supported if the VIRTCHNL2_CAP_PTP is negotiated during the capabilities recognition. Initial PTP support includes PTP initialization and registration of the clock. Reviewed-by: Alexander Lobakin Signed-off-by: Milena Olech --- drivers/net/ethernet/intel/idpf/Kconfig | 1 +

[Intel-wired-lan] [PATCH iwl-net 03/10] idpf: move virtchnl structures to the header file

2024-11-13 Thread Milena Olech
Move virtchnl strucutres to the header file to expose them for the PTP virtchnl file. Reviewed-by: Alexander Lobakin Signed-off-by: Milena Olech --- .../net/ethernet/intel/idpf/idpf_virtchnl.c | 86 +-- .../net/ethernet/intel/idpf/idpf_virtchnl.h | 84 ++ 2 f

[Intel-wired-lan] [PATCH iwl-net 07/10] idpf: add Tx timestamp capabilities negotiation

2024-11-13 Thread Milena Olech
Tx timestamp capabilities are negotiated for the uplink Vport. Driver receives information about the number of available Tx timestamp latches, the size of Tx timestamp value and the set of indexes used for Tx timestamping. Add function to get the Tx timestamp capabilities and parse the uplink vpor

[Intel-wired-lan] [PATCH 0/1] ixgbe: Correct BASE-BX10 compliance code

2024-11-13 Thread Tore Amundsen
The current code in ixgbe_82599 checks the SFP Ethernet compliance code against IXGBE_SFF_BASEBX10_CAPABLE to determine if an SFP module supports 1GB BASE-BX. According to SFF-8472 (section 5.4 Transceiver Compliance Codes), the BASE-BX10 bit is defined as bit 6, which corresponds to a value of 0x4

[Intel-wired-lan] [PATCH iwl-net 00/10] initial PTP support

2024-11-13 Thread Milena Olech
This patch series introduces support for Precision Time Protocol (PTP) to Intel(R) Infrastructure Data Path Function (IDPF) driver. PTP feature is supported when the PTP capability is negotiated with the Control Plane (CP). IDPF creates a PTP clock and sets a set of supported functions. During the

[Intel-wired-lan] [PATCH iwl-net 06/10] idpf: add PTP clock configuration

2024-11-13 Thread Milena Olech
PTP clock configuration operations - set time, adjust time and adjust frequency are required to control the clock and mantain synchronization process. Extend get PTP capabilities function to request for the clock adjustments and add functions to enable these actions using dedicated virtchnl messag

[Intel-wired-lan] [PATCH iwl-net 09/10] idpf: add support for Rx timestamping

2024-11-13 Thread Milena Olech
Add Rx timestamp function when the Rx timestamp value is read directly from the Rx descriptor. Add supported Rx timestamp modes. Reviewed-by: Alexander Lobakin Signed-off-by: Milena Olech --- drivers/net/ethernet/intel/idpf/idpf_ptp.c | 74 - drivers/net/ethernet/intel/idpf

[Intel-wired-lan] [PATCH iwl-net 10/10] idpf: change the method for mailbox workqueue allocation

2024-11-13 Thread Milena Olech
Since workqueues are created per CPU, the works scheduled to this workqueues are run on the CPU they were assigned. It may result in overloaded CPU that is not able to handle virtchnl messages in relatively short time. Allocating workqueue with WQ_UNBOUND and WQ_HIGHPRI flags allows scheduler to qu

[Intel-wired-lan] [PATCH 1/1] ixgbe: Correct BASE-BX10 compliance code

2024-11-13 Thread Tore Amundsen
SFF-8472 (section 5.4 Transceiver Compliance Codes) defines bit 6 as BASE-BX10. Bit 6 means a value of 0x40 (decimal 64). The current value in the source code is 0x64, which appears to be a mix-up of hex and decimal values. A value of 0x64 (binary 01100100) incorrectly sets bit 2 (1000BASE-CX) and

Re: [Intel-wired-lan] [iwl-next v7 5/9] ice, irdma: move interrupts code to irdma

2024-11-13 Thread Lukasz Czapnik
On 11/4/2024 1:13 PM, Michal Swiatkowski wrote: Move responsibility of MSI-X requesting for RDMA feature from ice driver to irdma driver. It is done to allow simple fallback when there is not enough MSI-X available. Change amount of MSI-X used for control from 4 to 1, as it isn't needed to ha

[Intel-wired-lan] [PATCH iwl-net 08/10] idpf: add Tx timestamp flows

2024-11-13 Thread Milena Olech
Add functions to request Tx timestamp for the PTP packets, read the Tx timestamp when the completion tag for that packet is being received, extend the Tx timestamp value and set the supported timestamping modes. Tx timestamp is requested for the PTP packets by setting a TSYN bit and index value in

[Intel-wired-lan] [PATCH iwl-net 02/10] virtchnl: add PTP virtchnl definitions

2024-11-13 Thread Milena Olech
PTP capabilities are negotiated using virtchnl commands. There are two available modes of the PTP support: direct and mailbox. When the direct access to PTP resources is negotiated, virtchnl messages returns a set of registers that allow read/write directly. When the mailbox access to PTP resources

[Intel-wired-lan] [PATCH iwl-net 04/10] idpf: negotiate PTP capabilies and get PTP clock

2024-11-13 Thread Milena Olech
PTP capabilities are negotiated using virtchnl command. Add get capabilities function, direct access to read the PTP clock time and direct access to read the cross timestamp - system time and PTP clock time. Set initial PTP capabilities exposed to the stack. Reviewed-by: Alexander Lobakin Signed-

[Intel-wired-lan] [PATCH iwl-net 05/10] idpf: add mailbox access to read PTP clock time

2024-11-13 Thread Milena Olech
When the access to read PTP clock is specified as mailbox, the driver needs to send virtchnl message to perform PTP actions. Message is sent using idpf_mbq_opc_send_msg_to_peer_drv mailbox opcode, with the parameters received during PTP capabilities negotiation. Add functions to recognize PTP mess

[Intel-wired-lan] [tnguy-net-queue:main] BUILD SUCCESS 73af53d82076bbe184d9ece9e14b0dc8599e6055

2024-11-13 Thread kernel test robot
i386 allyesconfigclang-19 i386buildonly-randconfig-001-20241113clang-19 i386buildonly-randconfig-002-20241113clang-19 i386buildonly-randconfig-003-20241113clang-19 i386buildonly-randconfig-004-20241113clang-19 i386buildonly-randconfig-005-202

[Intel-wired-lan] [PATCH net v1] ice: do not reserve resources for RDMA when disabled

2024-11-13 Thread jbrandeb
From: Jesse Brandeburg If the CONFIG_INFINIBAND_IRDMA symbol is not enabled as a module or a built-in, then don't let the driver reserve resources for RDMA. Do this by avoiding enabling the capability when scanning hardware capabilities. Fixes: d25a0fc41c1f ("ice: Initialize RDMA support") CC:

Re: [Intel-wired-lan] [iwl-next v7 5/9] ice, irdma: move interrupts code to irdma

2024-11-13 Thread Michal Swiatkowski
On Wed, Nov 13, 2024 at 05:21:20PM +0100, Lukasz Czapnik wrote: > > > On 11/4/2024 1:13 PM, Michal Swiatkowski wrote: > > Move responsibility of MSI-X requesting for RDMA feature from ice driver > > to irdma driver. It is done to allow simple fallback when there is not > > enough MSI-X available.

[Intel-wired-lan] [tnguy-next-queue:100GbE] BUILD SUCCESS e400c7444d84b0fd2ebb34e618f83abe05917543

2024-11-13 Thread kernel test robot
tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/tnguy/next-queue.git 100GbE branch HEAD: e400c7444d84b0fd2ebb34e618f83abe05917543 e1000: Hold RTNL when e1000_down can be called elapsed time: 742m configs tested: 82 configs skipped: 20 The following configs have been built success