<?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 sysfs-module</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>c04e9894 - xen: speed up grant-table reclaim</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#c04e9894</link>
        <description>xen: speed up grant-table reclaimWhen a grant entry is still in use by the remote domain, Linux must putit on a deferred list.  Normally, this list is very short, becausethe PV network and block protocols expect the backend to unmap the grantfirst.  However, Qubes OS&apos;s GUI protocol is subject to the constraintsof the X Window System, and as such winds up with the frontend unmappingthe window first.  As a result, the list can grow very large, resultingin a massive memory leak and eventual VM freeze.To partially solve this problem, make the number of entries that the VMwill attempt to free at each iteration tunable.  The default is still10, but it can be overridden via a module parameter.This is Cc: stable because (when combined with appropriate userspacechanges) it fixes a severe performance and stability problem for QubesOS users.Cc: stable@vger.kernel.orgSigned-off-by: Demi Marie Obenour &lt;demi@invisiblethingslab.com&gt;Reviewed-by: Juergen Gross &lt;jgross@suse.com&gt;Link: https://lore.kernel.org/r/20230726165354.1252-1-demi@invisiblethingslab.comSigned-off-by: Juergen Gross &lt;jgross@suse.com&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Wed, 26 Jul 2023 16:52:41 +0000</pubDate>
        <dc:creator>Demi Marie Obenour &lt;demi@invisiblethingslab.com&gt;</dc:creator>
    </item>
<item>
        <title>eeac9faf - ABI: testing/sysfs-module: document initstate</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#eeac9faf</link>
        <description>ABI: testing/sysfs-module: document initstateDespite being an old ABI, present on all modules, its documentationis missing. Add it, based on the original commit.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/b9c72187abce2b0efd1c41646b1d0c66104d90e4.1632750608.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Mon, 27 Sep 2021 13:59:36 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>6f3bceba - docs: ABI: remove some spurious characters</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#6f3bceba</link>
        <description>docs: ABI: remove some spurious charactersThe KernelVersion tag contains some spurious UTF-8 charactersfor no reason. Drop them.Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/6d774ad6cb3795a177309503a39f8f1b5e309d64.1620744606.git.mchehab+huawei@kernel.orgSigned-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Tue, 11 May 2021 15:01:30 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>4ec0b092 - docs: ABI: Drop trailing whitespace</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#4ec0b092</link>
        <description>docs: ABI: Drop trailing whitespaceRemove all trailing whitespace from the ABI documentation.Most of it was introduced during recent updates.Signed-off-by: Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;Link: https://lore.kernel.org/r/20201110144033.3278499-1-geert+renesas@glider.beSigned-off-by: Jonathan Corbet &lt;corbet@lwn.net&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Tue, 10 Nov 2020 14:40:33 +0000</pubDate>
        <dc:creator>Geert Uytterhoeven &lt;geert+renesas@glider.be&gt;</dc:creator>
    </item>
<item>
        <title>54a19b4d - docs: ABI: cleanup several ABI documents</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#54a19b4d</link>
        <description>docs: ABI: cleanup several ABI documentsThere are some ABI documents that, while they don&apos;t generateany warnings, they have issues when parsed by get_abi.pl scripton its output result.Address them, in order to provide a clean output.Reviewed-by: Tom Rix &lt;trix@redhat.com&gt; # for fpga-managerReviewed-By: Kajol Jain&lt;kjain@linux.ibm.com&gt; # for sysfs-bus-event_source-devices-hv_gpci and sysfs-bus-event_source-devices-hv_24x7Acked-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt; #for IIOAcked-by: Oded Gabbay &lt;oded.gabbay@gmail.com&gt; # for HabanalabsAcked-by: Vaibhav Jain &lt;vaibhav@linux.ibm.com&gt; # for sysfs-bus-papr-pmemAcked-by: Cezary Rojewski &lt;cezary.rojewski@intel.com&gt; # for catptAcked-by: Suzuki K Poulose &lt;suzuki.poulose@arm.com&gt;Acked-by: Ilya Dryomov &lt;idryomov@gmail.com&gt; # for rbdAcked-by: Jonathan Corbet &lt;corbet@lwn.net&gt;Signed-off-by: Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;Link: https://lore.kernel.org/r/5bc78e5b68ed1e9e39135173857cb2e753be868f.1604042072.git.mchehab+huawei@kernel.orgSigned-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Fri, 30 Oct 2020 07:40:50 +0000</pubDate>
        <dc:creator>Mauro Carvalho Chehab &lt;mchehab+huawei@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>57673c2b - Use &apos;E&apos; instead of &apos;X&apos; for unsigned module taint flag.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#57673c2b</link>
        <description>Use &apos;E&apos; instead of &apos;X&apos; for unsigned module taint flag.Takashi Iwai &lt;tiwai@suse.de&gt; says:&gt; The letter &apos;X&apos; has been already used for SUSE kernels for very long&gt; time, to indicate the external supported modules.  Can the new flag be&gt; changed to another letter for avoiding conflict...?&gt; (BTW, we also use &apos;N&apos; for &quot;no support&quot;, too.)Note: this code should be cleaned up, so we don&apos;t have such maps inthree places!Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Mon, 31 Mar 2014 04:09:57 +0000</pubDate>
        <dc:creator>Rusty Russell &lt;rusty@rustcorp.com.au&gt;</dc:creator>
    </item>
<item>
        <title>66cc69e3 - Fix: module signature vs tracepoints: add new TAINT_UNSIGNED_MODULE</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#66cc69e3</link>
        <description>Fix: module signature vs tracepoints: add new TAINT_UNSIGNED_MODULEUsers have reported being unable to trace non-signed modules loadedwithin a kernel supporting module signature.This is caused by tracepoint.c:tracepoint_module_coming() refusing totake into account tracepoints sitting within force-loaded modules(TAINT_FORCED_MODULE). The reason for this check, in the first place, isthat a force-loaded module may have a struct module incompatible withthe layout expected by the kernel, and can thus cause a kernel crashupon forced load of that module on a kernel with CONFIG_TRACEPOINTS=y.Tracepoints, however, specifically accept TAINT_OOT_MODULE andTAINT_CRAP, since those modules do not lead to the &quot;very likely systemcrash&quot; issue cited above for force-loaded modules.With kernels having CONFIG_MODULE_SIG=y (signed modules), a non-signedmodule is tainted re-using the TAINT_FORCED_MODULE taint flag.Unfortunately, this means that Tracepoints treat that module as aforce-loaded module, and thus silently refuse to consider any tracepointwithin this module.Since an unsigned module does not fit within the &quot;very likely systemcrash&quot; category of tainting, add a new TAINT_UNSIGNED_MODULE taint flagto specifically address this taint behavior, and accept those moduleswithin Tracepoints. We use the letter &apos;X&apos; as a taint flag character fora module being loaded that doesn&apos;t know how to sign its name (proposedby Steven Rostedt).Also add the missing &apos;O&apos; entry to trace event show_module_flags() listfor the sake of completeness.Signed-off-by: Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;Acked-by: Steven Rostedt &lt;rostedt@goodmis.org&gt;NAKed-by: Ingo Molnar &lt;mingo@redhat.com&gt;CC: Thomas Gleixner &lt;tglx@linutronix.de&gt;CC: David Howells &lt;dhowells@redhat.com&gt;CC: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Thu, 13 Mar 2014 01:41:30 +0000</pubDate>
        <dc:creator>Mathieu Desnoyers &lt;mathieu.desnoyers@efficios.com&gt;</dc:creator>
    </item>
<item>
        <title>cca3e707 - modules: sysfs - export: taint, coresize, initsize</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#cca3e707</link>
        <description>modules: sysfs - export: taint, coresize, initsizeRecent tools do not want to use /proc to retrieve module information. A fewvalues are currently missing from sysfs to replace the information availablein /proc/modules.This adds /sys/module/*/{coresize,initsize,taint} attributes.TAINT_PROPRIETARY_MODULE (P) and TAINT_OOT_MODULE (O) flags are both alwaysshown now, and do no longer exclude each other, also in /proc/modules.Replace the open-coded sysfs attribute initializers with the __ATTR() macro.Add the new attributes to Documentation/ABI.Cc: Lucas De Marchi &lt;lucas.demarchi@profusion.mobi&gt;Signed-off-by: Kay Sievers &lt;kay.sievers@vrfy.org&gt;Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Thu, 12 Jan 2012 23:02:15 +0000</pubDate>
        <dc:creator>Kay Sievers &lt;kay.sievers@vrfy.org&gt;</dc:creator>
    </item>
<item>
        <title>cc62a7eb - USB: EHCI: Allow users to override 80% max periodic bandwidth</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#cc62a7eb</link>
        <description>USB: EHCI: Allow users to override 80% max periodic bandwidthThere are cases, when 80% max isochronous bandwidth is too limiting.For example I have two USB video capture cards which stream uncompressedvideo, and to stream full NTSC + PAL videos we&apos;d need    NTSC 640x480 YUV422 @30fps      ~17.6 MB/s    PAL  720x576 YUV422 @25fps      ~19.7 MB/sisoc bandwidth.Now, due to limited alt settings in capture devices NTSC one ends upstreaming with max_pkt_size=2688  and  PAL with max_pkt_size=2892, bothwith interval=1. In terms of microframe time allocation this gives    NTSC    ~53us    PAL     ~57usand together    ~110us  &gt;  100us == 80% of 125us uframe time.So those two devices can&apos;t work together simultaneously because the&apos;dover allocate isochronous bandwidth.80% seemed a bit arbitrary to me, and I&apos;ve tried to raise it to 90% andboth devices started to work together, so I though sometimes it would bea good idea for users to override hardcoded default of max 80% isocbandwidth.After all, isn&apos;t it a user who should decide how to load the bus? If Ican live with 10% or even 5% bulk bandwidth that should be ok. I&apos;m a USBnewcomer, but that 80% set in stone by USB 2.0 specification seems to bechosen pretty arbitrary to me, just to serve as a reasonable default.NOTE 1~~~~~~for two streams with max_pkt_size=3072 (worst case) both timeallocation would be 60us+60us=120us which is 96% periodic bandwidthleaving 4% for bulk and control.  Alan Stern suggested that bulk thenwould be problematic (less than 300*8 bittimes left per microframe), butI think that is still enough for control traffic.NOTE 2~~~~~~Sarah Sharp expressed concern that maxing out periodic bandwidthcould lead to vendor-specific hardware bugs on host controllers, because&gt; It&apos;s entirely possible that you&apos;ll run into&gt; vendor-specific bugs if you try to pack the schedule with isochronous&gt; transfers.  I don&apos;t think any hardware designer would seriously test or&gt; validate their hardware with a schedule that is basically a violation of&gt; the USB bus spec (more than 80% for periodic transfers).So far I&apos;ve only tested this patch on my HP Mini 5103 with N10 chipset    kirr@mini:~$ lspci    00:00.0 Host bridge: Intel Corporation N10 Family DMI Bridge    00:02.0 VGA compatible controller: Intel Corporation N10 Family Integrated Graphics Controller    00:02.1 Display controller: Intel Corporation N10 Family Integrated Graphics Controller    00:1b.0 Audio device: Intel Corporation N10/ICH 7 Family High Definition Audio Controller (rev 02)    00:1c.0 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 1 (rev 02)    00:1c.3 PCI bridge: Intel Corporation N10/ICH 7 Family PCI Express Port 4 (rev 02)    00:1d.0 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #1 (rev 02)    00:1d.1 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #2 (rev 02)    00:1d.2 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #3 (rev 02)    00:1d.3 USB Controller: Intel Corporation N10/ICH 7 Family USB UHCI Controller #4 (rev 02)    00:1d.7 USB Controller: Intel Corporation N10/ICH 7 Family USB2 EHCI Controller (rev 02)    00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev e2)    00:1f.0 ISA bridge: Intel Corporation NM10 Family LPC Controller (rev 02)    00:1f.2 SATA controller: Intel Corporation N10/ICH7 Family SATA AHCI Controller (rev 02)    01:00.0 Network controller: Broadcom Corporation BCM4313 802.11b/g/n Wireless LAN Controller (rev 01)    02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8059 PCI-E Gigabit Ethernet Controller (rev 11)and the system works stable with 110us/uframe (~88%) isoc bandwith allocated forabove-mentioned isochronous transfers.NOTE 3~~~~~~This feature is off by default. I mean max periodic bandwidth is set to100us/uframe by default exactly as it was before the patch. So only those of uswho need the extreme settings are taking the risk - normal users who do notalter uframe_periodic_max sysfs attribute should not see any change at all.NOTE 4~~~~~~I&apos;ve tried to update documentation in Documentation/ABI/ thoroughly, butonly &quot;TBD&quot; was put into Documentation/usb/ehci.txt -- the text there seemsto be outdated and much needing refreshing, before it could be amended.Cc: Sarah Sharp &lt;sarah.a.sharp@linux.intel.com&gt;Signed-off-by: Kirill Smelkov &lt;kirr@mns.spb.ru&gt;Acked-by: Alan Stern &lt;stern@rowland.harvard.edu&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Sun, 03 Jul 2011 16:36:57 +0000</pubDate>
        <dc:creator>Kirill Smelkov &lt;kirr@mns.spb.ru&gt;</dc:creator>
    </item>
<item>
        <title>cf4ece53 - add Packet hub driver for Topcliff Platform controller hub</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/Documentation/ABI/testing/sysfs-module#cf4ece53</link>
        <description>add Packet hub driver for Topcliff Platform controller hubPacket hub driver of Topcliff PCHTopcliff PCH is the platform controller hub that is going to be used inIntel&apos;s upcoming general embedded platform. All IO peripherals inTopcliff PCH are actually devices sitting on AMBA bus. Packet hub isa special converter device in Topcliff PCH that translate AMBA transactionsto PCI Express transactions and vice versa. Thus packet hub helps presentall IO peripherals in Topcliff PCH as PCIE devices to IA system.Topcliff PCH has MAC address and Option ROM data.These data are in SROM which is connected to PCIE bus.Packet hub driver of Topcliff PCH can access MAC address and Option ROM data inSROM via sysfs interface.Signed-off-by: Greg Kroah-Hartman &lt;gregkh@suse.de&gt;

            List of files:
            /linux-6.15/Documentation/ABI/testing/sysfs-module</description>
        <pubDate>Wed, 01 Sep 2010 12:16:30 +0000</pubDate>
        <dc:creator>Masayuki Ohtak &lt;masa-korg@dsn.okisemi.com&gt;</dc:creator>
    </item>
</channel>
</rss>
