<?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 Kbuild</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>68deb997 - tools/testing/cxl: Disable &quot;missing prototypes / declarations&quot; warnings</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/cxl/test/Kbuild#68deb997</link>
        <description>tools/testing/cxl: Disable &quot;missing prototypes / declarations&quot; warningsPrevent warnings of the form:tools/testing/cxl/test/mock.c:44:6: error: no previous prototype for&#8216;__wrap_is_acpi_device_node&#8217; [-Werror=missing-prototypes]tools/testing/cxl/test/mock.c:63:5: error: no previous prototype for&#8216;__wrap_acpi_table_parse_cedt&#8217; [-Werror=missing-prototypes]tools/testing/cxl/test/mock.c:81:13: error: no previous prototype for&#8216;__wrap_acpi_evaluate_integer&#8217; [-Werror=missing-prototypes]...by locally disabling some warnings.It turns out that:Commit 0fcb70851fbf (&quot;Makefile.extrawarn: turn on missing-prototypes globally&quot;)...in addition to expanding in-tree coverage, also impacts out-of-treemodule builds like those in tools/testing/cxl/.Filter out the warning options on unit test code that does not effectmainline builds.Reviewed-by: Alison Schofield &lt;alison.schofield@intel.com&gt;Link: https://lore.kernel.org/r/170543983780.460832.10920261849128601697.stgit@dwillia2-xfh.jf.intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/tools/testing/cxl/test/Kbuild</description>
        <pubDate>Tue, 16 Jan 2024 21:17:17 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>d1dca858 - cxl/test: Add generic mock events</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/cxl/test/Kbuild#d1dca858</link>
        <description>cxl/test: Add generic mock eventsFacilitate testing basic Get/Clear Event functionality by creatingmultiple logs and generic events with made up UUID&apos;s.Data is completely made up with data patterns which should be easy tospot in trace output.A single sysfs entry resets the event data and triggers collecting theevents for testing.Test traces are easy to obtain with a small script such as this:	#!/bin/bash -x	devices=`find /sys/devices/platform -name cxl_mem*`	# Turn on tracing	echo &quot;&quot; &gt; /sys/kernel/tracing/trace	echo 1 &gt; /sys/kernel/tracing/events/cxl/enable	echo 1 &gt; /sys/kernel/tracing/tracing_on	# Generate fake interrupt	for device in $devices; do	        echo 1 &gt; $device/event_trigger	done	# Turn off tracing and report events	echo 0 &gt; /sys/kernel/tracing/tracing_on	cat /sys/kernel/tracing/traceReviewed-by: Dan Williams &lt;dan.j.williams@intel.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Ira Weiny &lt;ira.weiny@intel.com&gt;Link: https://lore.kernel.org/r/20221216-cxl-ev-log-v7-6-2316a5c8f7d8@intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/tools/testing/cxl/test/Kbuild</description>
        <pubDate>Wed, 18 Jan 2023 05:53:41 +0000</pubDate>
        <dc:creator>Ira Weiny &lt;ira.weiny@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>7d3eb23c - tools/testing/cxl: Introduce a mock memory device + driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/cxl/test/Kbuild#7d3eb23c</link>
        <description>tools/testing/cxl: Introduce a mock memory device + driverIntroduce an emulated device-set plus driver to register CXL memorydevices, &apos;struct cxl_memdev&apos; instances, in the mock cxl_test topology.This enables the development of HDM Decoder (Host-managed Device MemoryDecoder) programming flow (region provisioning) in an environment thatcan be updated alongside the kernel as it gains more functionality.Whereas the cxl_pci module looks for CXL memory expanders on the &apos;pci&apos;bus, the cxl_mock_mem module attaches to CXL expanders on the platformbus emitted by cxl_test.Acked-by: Ben Widawsky &lt;ben.widawsky@intel.com&gt;Reported-by: kernel test robot &lt;lkp@intel.com&gt;Reviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Link: https://lore.kernel.org/r/163116440099.2460985.10692549614409346604.stgit@dwillia2-desk3.amr.corp.intel.comSigned-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/tools/testing/cxl/test/Kbuild</description>
        <pubDate>Thu, 09 Sep 2021 05:13:21 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>67dcdd4d - tools/testing/cxl: Introduce a mocked-up CXL port hierarchy</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/tools/testing/cxl/test/Kbuild#67dcdd4d</link>
        <description>tools/testing/cxl: Introduce a mocked-up CXL port hierarchyCreate an environment for CXL plumbing unit tests. Especially when itcomes to an algorithm for HDM Decoder (Host-managed Device MemoryDecoder) programming, the availability of an in-kernel-tree emulationenvironment for CXL configuration complexity and corner cases speedsdevelopment and deters regressions.The approach taken mirrors what was done for tools/testing/nvdimm/. I.e.an external module, cxl_test.ko built out of the tools/testing/cxl/directory, provides mock implementations of kernel APIs and kernelobjects to simulate a real world device hierarchy.One feedback for the tools/testing/nvdimm/ proposal was &quot;why not do thisin QEMU?&quot;. In fact, the CXL development community has developed a QEMUmodel for CXL [1]. However, there are a few blocking issues that keepQEMU from being a tight fit for topology + provisioning unit tests:1/ The QEMU community has yet to show interest in merging any of this   support that has had patches on the list since November 2020. So,   testing CXL to date involves building custom QEMU with out-of-tree   patches.2/ CXL mechanisms like cross-host-bridge interleave do not have a clear   path to be emulated by QEMU without major infrastructure work. This   is easier to achieve with the alloc_mock_res() approach taken in this   patch to shortcut-define emulated system physical address ranges with   interleave behavior.The QEMU enabling has been critical to get the driver off the ground,and may still move forward, but it does not address the ongoing needs ofa regression testing environment and test driven development.This patch adds an ACPI CXL Platform definition with emulated CXLmulti-ported host-bridges. A follow on patch adds emulated memoryexpander devices.Acked-by: Ben Widawsky &lt;ben.widawsky@intel.com&gt;Reported-by: Vishal Verma &lt;vishal.l.verma@intel.com&gt;Link: https://lore.kernel.org/r/20210202005948.241655-1-ben.widawsky@intel.com [1]Link: https://lore.kernel.org/r/163164680798.2831381.838684634806668012.stgit@dwillia2-desk3.amr.corp.intel.comReviewed-by: Jonathan Cameron &lt;Jonathan.Cameron@huawei.com&gt;Signed-off-by: Dan Williams &lt;dan.j.williams@intel.com&gt;

            List of files:
            /linux-6.15/tools/testing/cxl/test/Kbuild</description>
        <pubDate>Tue, 14 Sep 2021 19:14:22 +0000</pubDate>
        <dc:creator>Dan Williams &lt;dan.j.williams@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
