<?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 README</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>07496eea - tools/virtio: use canonical ftrace path</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/virtio/virtio-trace/README#07496eea</link>
        <description>tools/virtio: use canonical ftrace pathThe canonical location for the tracefs filesystem is at /sys/kernel/tracing.But, from Documentation/trace/ftrace.rst:  Before 4.1, all ftrace tracing control files were within the debugfs  file system, which is typically located at /sys/kernel/debug/tracing.  For backward compatibility, when mounting the debugfs file system,  the tracefs file system will be automatically mounted at:  /sys/kernel/debug/tracingA few spots in tools/virtio still refer to this older debugfspath, so let&apos;s update them to avoid confusion.Signed-off-by: Ross Zwisler &lt;zwisler@google.com&gt;Message-Id: &lt;20230215223350.2658616-6-zwisler@google.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Reviewed-by: Mukesh Ojha &lt;quic_mojha@quicinc.com&gt;

            List of files:
            /linux-6.15/tools/virtio/virtio-trace/README</description>
        <pubDate>Wed, 15 Feb 2023 22:33:49 +0000</pubDate>
        <dc:creator>Ross Zwisler &lt;zwisler@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>9513c55c - tools/virtio: fix typo in README instructions</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/virtio/virtio-trace/README#9513c55c</link>
        <description>tools/virtio: fix typo in README instructionsWe need to have a unique chardev for each data path, else the chardevswill collide and qemu will die with this message:  qemu-system-x86_64: -device  virtserialport,bus=virtio-serial0.0,nr=2,chardev=charchannel0,  id=channel1,name=trace-path-cpu0:  Property &apos;virtserialport.chardev&apos; can&apos;t take value &apos;charchannel0&apos;:  Device &apos;charchannel0&apos; is in useSigned-off-by: Ross Zwisler &lt;zwisler@google.com&gt;Message-Id: &lt;20230215223350.2658616-7-zwisler@google.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/tools/virtio/virtio-trace/README</description>
        <pubDate>Wed, 15 Feb 2023 22:33:50 +0000</pubDate>
        <dc:creator>Ross Zwisler &lt;zwisler@chromium.org&gt;</dc:creator>
    </item>
<item>
        <title>108fc825 - tools: Add guest trace agent as a user tool</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/virtio/virtio-trace/README#108fc825</link>
        <description>tools: Add guest trace agent as a user toolThis patch adds a user tool, &quot;trace agent&quot; for sending trace data of a guest toa Host in low overhead. This agent has the following functions: - splice a page of ring-buffer to read_pipe without memory copying - splice the page from write_pipe to virtio-console without memory copying - write trace data to stdout by using -o option - controlled by start/stop orders from a HostChanges in v2: - Cleanup (change fprintf() to pr_err() and an include guard)Signed-off-by: Yoshihiro YUNOMAE &lt;yoshihiro.yunomae.ez@hitachi.com&gt;Acked-by: Amit Shah &lt;amit.shah@redhat.com&gt;Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;

            List of files:
            /linux-6.15/tools/virtio/virtio-trace/README</description>
        <pubDate>Thu, 09 Aug 2012 12:31:30 +0000</pubDate>
        <dc:creator>Yoshihiro YUNOMAE &lt;yoshihiro.yunomae.ez@hitachi.com&gt;</dc:creator>
    </item>
</channel>
</rss>
