<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in Makefile</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>4d09dd11 - pds_fwctl: initial driver framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/fwctl/Makefile#4d09dd11</link>
        <description>pds_fwctl: initial driver frameworkInitial files for adding a new fwctl driver for the AMD/Pensando PDSdevices.  This sets up a simple auxiliary_bus driver that registerswith fwctl subsystem.  It expects that a pds_core device has set upthe auxiliary_device pds_core.fwctlLink: https://patch.msgid.link/r/20250320194412.67983-5-shannon.nelson@amd.comReviewed-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;Reviewed-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/fwctl/Makefile</description>
        <pubDate>Thu, 20 Mar 2025 19:44:10 +0000</pubDate>
        <dc:creator>Shannon Nelson &lt;shannon.nelson@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>52929c21 - fwctl/mlx5: Support for communicating with mlx5 fw</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/fwctl/Makefile#52929c21</link>
        <description>fwctl/mlx5: Support for communicating with mlx5 fwmlx5 FW has a built in security context called UID. Each UID has a set ofpermissions controlled by the kernel when it is created and every commandis tagged by the kernel with a particular UID. In general commands cannotreach objects outside of their UID and commands cannot exceed their UID&apos;spermissions. These restrictions are enforced by FW.This mechanism has long been used in RDMA for the devx interface whereRDMA will sent commands directly to the FW and the UID limitationsrestrict those commands to a ib_device/verbs security domain. For instancecommands that would effect other VFs, or global device resources. Themodel is suitable for unprivileged userspace to operate the RDMAfunctionality.The UID has been extended with a &quot;tools resources&quot; permission which allowsadditional commands and sub-commands that are intended to match with thescope limitations set in FWCTL. This is an alternative design to the&quot;command intent log&quot; where the FW does the enforcement rather than havingthe FW report the enforcement the kernel should do.Consistent with the fwctl definitions the &quot;tools resources&quot; securitycontext is limited to the FWCTL_RPC_CONFIGURATION,FWCTL_RPC_DEBUG_READ_ONLY, FWCTL_RPC_DEBUG_WRITE, andFWCTL_RPC_DEBUG_WRITE_FULL security scopes.Like RDMA devx, each opened fwctl file descriptor will get a unique UIDassociated with each file descriptor.The fwctl driver is kept simple and we reject commands that can createobjects as the UID mechanism relies on the kernel to track and destroyobjects prior to detroying the UID. Filtering into fwctl sub scopes isdone inside the driver with a switch statement. This substantially limitswhat is possible to primarily query functions ad a few limited setoperations.mlx5 already has a robust infrastructure for delivering RPC messages tofw. Trivially connect fwctl&apos;s RPC mechanism to mlx5_cmd_do(). Enforce theUser Context ID in every RPC header accepted from the FD so the FW knowsthe security context of the issuing ID.Link: https://patch.msgid.link/r/7-v5-642aa0c94070+4447f-fwctl_jgg@nvidia.comReviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Saeed Mahameed &lt;saeedm@nvidia.com&gt;Reviewed-by: Leon Romanovsky &lt;leonro@nvidia.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/fwctl/Makefile</description>
        <pubDate>Fri, 28 Feb 2025 00:26:35 +0000</pubDate>
        <dc:creator>Saeed Mahameed &lt;saeedm@nvidia.com&gt;</dc:creator>
    </item>
<item>
        <title>2e4986cf - fwctl: Add basic structure for a class subsystem with a cdev</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/fwctl/Makefile#2e4986cf</link>
        <description>fwctl: Add basic structure for a class subsystem with a cdevCreate the class, character device and functions for a fwctl driver toun/register to the subsystem.A typical fwctl driver has a sysfs presence like:$ ls -l /dev/fwctl/fwctl0crw------- 1 root root 250, 0 Apr 25 19:16 /dev/fwctl/fwctl0$ ls /sys/class/fwctl/fwctl0dev  device  power  subsystem  uevent$ ls /sys/class/fwctl/fwctl0/device/infiniband/ibp0s10f0$ ls /sys/class/infiniband/ibp0s10f0/device/fwctl/fwctl0/$ ls /sys/devices/pci0000:00/0000:00:0a.0/fwctl/fwctl0dev  device  power  subsystem  ueventWhich allows userspace to link all the multi-subsystem driver componentstogether and learn the subsystem specific names for the device&apos;scomponents.Link: https://patch.msgid.link/r/1-v5-642aa0c94070+4447f-fwctl_jgg@nvidia.comReviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Reviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Reviewed-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Tested-by: Dave Jiang &lt;dave.jiang@intel.com&gt;Tested-by: Shannon Nelson &lt;shannon.nelson@amd.com&gt;Signed-off-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;

            List of files:
            /linux-6.15/drivers/fwctl/Makefile</description>
        <pubDate>Fri, 28 Feb 2025 00:26:29 +0000</pubDate>
        <dc:creator>Jason Gunthorpe &lt;jgg@nvidia.com&gt;</dc:creator>
    </item>
</channel>
</rss>
