<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/source/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in sysfs-bus-event_source-devices</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>1260ed77798502de9c98020040d2995008de10cc - Merge drm/drm-fixes into drm-misc-fixes</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#1260ed77798502de9c98020040d2995008de10cc</link>
        <description>Merge drm/drm-fixes into drm-misc-fixesBackmerging to get updates from v6.15-rc1.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Tue, 08 Apr 2025 10:15:47 +0200</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>946661e3bef8efa11ba8079d4ebafe6fc3b0aaad - Merge branch &apos;next&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#946661e3bef8efa11ba8079d4ebafe6fc3b0aaad</link>
        <description>Merge branch &apos;next&apos; into for-linusPrepare input updates for 6.15 merge window.

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Sat, 05 Apr 2025 08:04:35 +0200</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0b119045b79a672bc6d8f18641c60fc8ce1b4585 - Merge tag &apos;v6.14-rc4&apos; into next</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#0b119045b79a672bc6d8f18641c60fc8ce1b4585</link>
        <description>Merge tag &apos;v6.14-rc4&apos; into nextSync up with the mainline.

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Wed, 26 Feb 2025 01:03:25 +0100</pubDate>
        <dc:creator>Dmitry Torokhov &lt;dmitry.torokhov@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>0410c6121529409b08e81a77ae3ee58c657e2243 - Merge drm/drm-next into drm-xe-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#0410c6121529409b08e81a77ae3ee58c657e2243</link>
        <description>Merge drm/drm-next into drm-xe-nextSync to fix conlicts between drm-xe-next and drm-intel-next.Signed-off-by: Lucas De Marchi &lt;lucas.demarchi@intel.com&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Fri, 28 Feb 2025 15:54:14 +0100</pubDate>
        <dc:creator>Lucas De Marchi &lt;lucas.demarchi@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>93c7dd1b39444ebd5a6a98e56a363d7a4e646775 - Merge drm/drm-next into drm-misc-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#93c7dd1b39444ebd5a6a98e56a363d7a4e646775</link>
        <description>Merge drm/drm-next into drm-misc-nextBring rc1 to start the new release dev.Signed-off-by: Maxime Ripard &lt;mripard@kernel.org&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Thu, 06 Feb 2025 13:47:32 +0100</pubDate>
        <dc:creator>Maxime Ripard &lt;mripard@kernel.org&gt;</dc:creator>
    </item>
<item>
        <title>ea9f8f2b21795a5d80418a655bcb212d5b89e08f - Merge drm/drm-next into drm-intel-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#ea9f8f2b21795a5d80418a655bcb212d5b89e08f</link>
        <description>Merge drm/drm-next into drm-intel-nextSync with v6.14-rc1.Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Wed, 05 Feb 2025 18:12:37 +0100</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>c771600c6af14749609b49565ffb4cac2959710d - Merge drm/drm-next into drm-intel-gt-next</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#c771600c6af14749609b49565ffb4cac2959710d</link>
        <description>Merge drm/drm-next into drm-intel-gt-nextWe need4ba4f1afb6a9 (&quot;perf: Generic hotplug support for a PMU with a scope&quot;)in order to land a i915 PMU simplification and a fix. That landed in 6.12and we are stuck at 6.9 so lets bump things forward.Signed-off-by: Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Wed, 05 Feb 2025 10:29:14 +0100</pubDate>
        <dc:creator>Tvrtko Ursulin &lt;tursulin@ursulin.net&gt;</dc:creator>
    </item>
<item>
        <title>b3cc7428a32202936904b5b07cf9f135025bafd6 - Merge branch &apos;for-6.15/amd_sfh&apos; into for-linus</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#b3cc7428a32202936904b5b07cf9f135025bafd6</link>
        <description>Merge branch &apos;for-6.15/amd_sfh&apos; into for-linusFrom: Mario Limonciello &lt;mario.limonciello@amd.com&gt;Some platforms include a human presence detection (HPD) sensor. Whenenabled and a user is detected a wake event will be emitted from thesensor fusion hub that software can react to.Example use cases are &quot;wake from suspend on approach&quot; or to &quot;lockwhen leaving&quot;.This is currently enabled by default on supported systems, but userscan&apos;t control it. This essentially means that wake on approach isenabled which is a really surprising behavior to users that don&apos;texpect it.Instead of defaulting to enabled add a sysfs knob that users canuse to enable the feature if desirable and set it to disabled bydefault.

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Wed, 26 Mar 2025 13:42:07 +0100</pubDate>
        <dc:creator>Jiri Kosina &lt;jkosina@suse.com&gt;</dc:creator>
    </item>
<item>
        <title>7685b334d1e4927cc73b62c65293ba65748d9c52 - Merge tag &apos;perf-tools-for-v6.14-2025-01-21&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#7685b334d1e4927cc73b62c65293ba65748d9c52</link>
        <description>Merge tag &apos;perf-tools-for-v6.14-2025-01-21&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-toolsPull perf-tools updates from Namhyung Kim: &quot;There are a lot of changes in the perf tools in this cycle.  build:   - Use generic syscall table to generate syscall numbers on supported     archs   - This also enables to get rid of libaudit which was used for syscall     numbers   - Remove python2 support as it&apos;s deprecated for years   - Fix issues on static build with libzstd  perf record:   - Intel-PT supports &quot;aux-action&quot; config term to pause or resume     tracing in the aux-buffer. Users can start the intel_pt event as     &quot;started-paused&quot; and configure other events to control the Intel-PT     tracing:         # perf record --kcore -e intel_pt/aux-action=start-paused/   \             -e syscalls:sys_enter_newuname/aux-action=resume/        \             -e syscalls:sys_exit_newuname/aux-action=pause/ -- uname     This requires kernel support (which was added in v6.13)  perf lock:   - &apos;perf lock contention&apos; command has an ability to symbolize locks in     dynamically allocated objects using slab cache name when it runs     with BPF. Those dynamic locks would have &quot;&amp;&quot; prefix in the name to     distinguish them from ordinary (static) locks        # perf lock con -abl -E 5 sleep 1           contended   total wait     max wait     avg wait            address   symbol                   2      1.95 us      1.77 us       975 ns   ffff9d5e852d3498   &amp;task_struct (mutex)                   1      1.18 us      1.18 us      1.18 us   ffff9d5e852d3538   &amp;task_struct (mutex)                   4      1.12 us       354 ns       279 ns   ffff9d5e841ca800   &amp;kmalloc-cg-512 (mutex)                   2       859 ns       617 ns       429 ns   ffffffffa41c3620   delayed_uprobe_lock (mutex)                   3       691 ns       388 ns       230 ns   ffffffffa41c0940   pack_mutex (mutex)     This also requires kernel/BPF support (which was added in v6.13)  perf ftrace:   - &apos;perf ftrace latency&apos; command gets a couple of options to support     linear buckets instead of exponential. Also it&apos;s possible to     specify max and min latency for the linear buckets:        # perf ftrace latency -abn -T switch_mm_irqs_off --bucket-range=100   \            --min-latency=200 --max-latency=800 -- sleep 1        #   DURATION     |      COUNT | GRAPH                                  |             0 -  200 ns |        186 | ###                                    |           200 -  300 ns |        256 | #####                                  |           300 -  400 ns |        364 | #######                                |           400 -  500 ns |        223 | ####                                   |           500 -  600 ns |        111 | ##                                     |           600 -  700 ns |         41 |                                        |           700 -  800 ns |        141 | ##                                     |           800 -  ... ns |        169 | ###                                    |        # statistics  (in nsec)          total time:              2162212            avg time:                  967            max time:                16817            min time:                  132               count:                 2236   - As you can see in the above example, it nows shows the statistics     at the end so that users can see the avg/max/min latencies easily   - &apos;perf ftrace profile&apos; command has --graph-opts option like &apos;perf     ftrace trace&apos; so that it can control the tracing behaviors in the     same way. For example, it can limit the function call depth or     threshold  perf script:   - Improve physical memory resolution in &apos;mem-phys-addr&apos; script by     parsing /proc/iomem file        # perf script mem-phys-addr -- find /        ...        Event: mem_inst_retired.all_loads:P        Memory type                                    count  percentage        ----------------------------------------  ----------  ----------        100000000-85f7fffff : System RAM                8929        69.7          547600000-54785d23f : Kernel data             1240         9.7          546a00000-5474bdfff : Kernel rodata            490         3.8          5480ce000-5485fffff : Kernel bss               121         0.9        0-fff : Reserved                                3860        30.1        100000-89c01fff : System RAM                      18         0.1        8a22c000-8df6efff : System RAM                     5         0.0  Others:   - &apos;perf test&apos; gets --runs-per-test option to run the test cases     repeatedly. This would be helpful to see if it&apos;s flaky   - Add &apos;parse_events&apos; method to Python perf extension module, so that     users can use the same event parsing logic in the python code. One     more step towards implementing perf tools in Python. :)   - Support opening tracepoint events without libtraceevent. This will     be helpful if it won&apos;t use the tracing data like in &apos;perf stat&apos;   - Update ARM Neoverse N2/V2 JSON events and metrics&quot;* tag &apos;perf-tools-for-v6.14-2025-01-21&apos; of git://git.kernel.org/pub/scm/linux/kernel/git/perf/perf-tools: (176 commits)  perf test: Update event_groups test to use instructions  perf bench: Fix undefined behavior in cmpworker()  perf annotate: Prefer passing evsel to evsel-&gt;core.idx  perf lock: Rename fields in lock_type_table  perf lock: Add percpu-rwsem for type filter  perf lock: Fix parse_lock_type which only retrieve one lock flag  perf lock: Fix return code for functions in __cmd_contention  perf hist: Fix width calculation in hpp__fmt()  perf hist: Fix bogus profiles when filters are enabled  perf hist: Deduplicate cmp/sort/collapse code  perf test: Improve verbose documentation  perf test: Add a runs-per-test flag  perf test: Fix parallel/sequential option documentation  perf test: Send list output to stdout rather than stderr  perf test: Rename functions and variables for better clarity  perf tools: Expose quiet/verbose variables in Makefile.perf  perf config: Add a function to set one variable in .perfconfig  perf test perftool_testsuite: Return correct value for skipping  perf test perftool_testsuite: Add missing description  perf test record+probe_libc_inet_pton: Make test resilient  ...

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Fri, 24 Jan 2025 14:45:40 +0100</pubDate>
        <dc:creator>Linus Torvalds &lt;torvalds@linux-foundation.org&gt;</dc:creator>
    </item>
<item>
        <title>518413d89ce498d35f6cb7104dd8c32f6e87a9aa - perf Documentation: Describe the PMU naming convention</title>
        <link>http://kernelsources.org:8080/source/history/linux/Documentation/ABI/testing/sysfs-bus-event_source-devices#518413d89ce498d35f6cb7104dd8c32f6e87a9aa</link>
        <description>perf Documentation: Describe the PMU naming conventionIt is an existing convention to use suffixes with PMU names. Try tocapture that convention so that future PMU devices may adhere to it.The name of the file and date within the file try to follow existingconventions, particularly sysfs-bus-event_source-devices-events.Reviewed-by: James Clark &lt;james.clark@arm.com&gt;Reviewed-by: Kan Liang &lt;kan.liang@linux.intel.com&gt;Reviewed-by: Leo Yan &lt;leo.yan@arm.com&gt;Reviewed-by: Randy Dunlap &lt;rdunlap@infradead.org&gt;Signed-off-by: Ian Rogers &lt;irogers@google.com&gt;Cc: Adrian Hunter &lt;adrian.hunter@intel.com&gt;Cc: Alexander Shishkin &lt;alexander.shishkin@linux.intel.com&gt;Cc: Bharat Bhushan &lt;bbhushan2@marvell.com&gt;Cc: Bhaskara Budiredla &lt;bbudiredla@marvell.com&gt;Cc: Ingo Molnar &lt;mingo@redhat.com&gt;Cc: Jiri Olsa &lt;jolsa@kernel.org&gt;Cc: Mark Rutland &lt;mark.rutland@arm.com&gt;Cc: Namhyung Kim &lt;namhyung@kernel.org&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Ravi Bangoria &lt;ravi.bangoria@amd.com&gt;Cc: Robin Murphy &lt;robin.murphy@arm.com&gt;Cc: Stephane Eranian &lt;eranian@google.com&gt;Cc: Thomas Richter &lt;tmricht@linux.ibm.com&gt;Cc: Tuan Phan &lt;tuanphan@os.amperecomputing.com&gt;Cc: Will Deacon &lt;will@kernel.org&gt;Link: https://lore.kernel.org/r/20240606044959.335715-1-irogers@google.comSigned-off-by: Arnaldo Carvalho de Melo &lt;acme@redhat.com&gt;

            List of files:
            /linux/Documentation/ABI/testing/sysfs-bus-event_source-devices</description>
        <pubDate>Thu, 06 Jun 2024 06:49:59 +0200</pubDate>
        <dc:creator>Ian Rogers &lt;irogers@google.com&gt;</dc:creator>
    </item>
</channel>
</rss>
