<?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>cd2eb57d - drm/vmwgfx: Implement virtual kms</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#cd2eb57d</link>
        <description>drm/vmwgfx: Implement virtual kmsBy default vmwgfx doesn&apos;t support vblanking or crc generation whichmakes it impossible to use various IGT tests to validate vmwgfx.Implement virtual kernel mode setting, which is mainly related tosimulated vblank support.Code is very similar to amd&apos;s vkms and the vkms module itself, exceptthat it&apos;s integrated with vmwgfx three different output technologies -legacy, screen object and screen targets.Make IGT&apos;s kms_vblank pass on vmwgfx and allows a lot of other IGTtests to run with vmwgfx.Support for vkms needs to be manually enabled by adding:guestinfo.vmwgfx.vkms_enable = &quot;TRUE&quot;somewhere in the vmx file, otherwise it&apos;s off by default.Signed-off-by: Zack Rusin &lt;zack.rusin@broadcom.com&gt;Acked-by: Martin Krastev &lt;martin.krastev@broadcom.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20240412025511.78553-2-zack.rusin@broadcom.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Fri, 12 Apr 2024 02:55:07 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zack.rusin@broadcom.com&gt;</dc:creator>
    </item>
<item>
        <title>9da2957f - drm/vmwgfx: Use the common gem mmap instead of the custom code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#9da2957f</link>
        <description>drm/vmwgfx: Use the common gem mmap instead of the custom codeBefore vmwgfx supported gem it needed to implement the entire mmap logicexplicitly. With GEM support that&apos;s not needed and the generic codecan be used by simply setting the vm_ops to vmwgfx specific ones on thegem object itself.Removes a lot of code from vmwgfx without any functional difference.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20230131033542.953249-2-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Tue, 31 Jan 2023 03:35:35 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>df42523c - drm/vmwgfx: Port the framebuffer code to drm fb helpers</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#df42523c</link>
        <description>drm/vmwgfx: Port the framebuffer code to drm fb helpersInstead of using vmwgfx specific framebuffer implementation use the drmfb helpers. There&apos;s no change in functionality, the only differenceis a reduction in the amount of code inside the vmwgfx module.drm fb helpers do not deal correctly with changes in crtc preferred modeat runtime, but the old fb code wasn&apos;t dealing with it either.Same situation applies to high-res fb consoles - the old code waslimited to 1176x885 because it was checking for legacy/deprecatedmemory limites, the drm fb helpers are limited to the initial resolutionset on fb due to first problem (drm fb helpers being unable to handlehotplug crtc preferred mode changes).This also removes the kernel config for disabling fb support which hasn&apos;tbeen used or supported in a very long time.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20221022040236.616490-14-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Sat, 22 Oct 2022 04:02:32 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>9da30cdd - drm/vmwgfx: Remove vmwgfx_hashtab</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#9da30cdd</link>
        <description>drm/vmwgfx: Remove vmwgfx_hashtabThe vmwgfx driver has migrated from using the hashtable in vmwgfx_hashtabto the linux/hashtable implementation. Remove the vmwgfx_hashtab from thedriver.Signed-off-by: Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20221022040236.616490-12-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Sat, 22 Oct 2022 04:02:30 +0000</pubDate>
        <dc:creator>Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>bc701a28 - drm/vmwgfx: Remove explicit transparent hugepages support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#bc701a28</link>
        <description>drm/vmwgfx: Remove explicit transparent hugepages supportOld versions of the svga device used to export virtual vram, handling ofwhich was optimized on top of transparent hugepages support. Only veryold devices (OpenGL 2.1 support and earlier) used this code and at thispoint performance differences are negligible.Because the code requires very old hardware versions to run it hasbeen largely untested and unused for a long time.Furthermore removal of the ttm hugepages support in:commit 0d979509539e (&quot;drm/ttm: remove ttm_bo_vm_insert_huge()&quot;)broke the coherency mode in vmwgfx when running with hugepages.Fixes: 0d979509539e (&quot;drm/ttm: remove ttm_bo_vm_insert_huge()&quot;)Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Cc: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Cc: Thomas Hellstr&#246;m &lt;thomas.hellstrom@linux.intel.com&gt;Cc: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Cc: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211215184147.3688785-2-zack@kde.org(cherry picked from commit 49d535d64d52945e2c874f380705675e20a02b6a)Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 15 Dec 2021 18:41:46 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>49d535d6 - drm/vmwgfx: Remove explicit transparent hugepages support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#49d535d6</link>
        <description>drm/vmwgfx: Remove explicit transparent hugepages supportOld versions of the svga device used to export virtual vram, handling ofwhich was optimized on top of transparent hugepages support. Only veryold devices (OpenGL 2.1 support and earlier) used this code and at thispoint performance differences are negligible.Because the code requires very old hardware versions to run it hasbeen largely untested and unused for a long time.Furthermore removal of the ttm hugepages support in:commit 0d979509539e (&quot;drm/ttm: remove ttm_bo_vm_insert_huge()&quot;)broke the coherency mode in vmwgfx when running with hugepages.Fixes: 0d979509539e (&quot;drm/ttm: remove ttm_bo_vm_insert_huge()&quot;)Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Cc: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Cc: Thomas Hellstr&#246;m &lt;thomas.hellstrom@linux.intel.com&gt;Cc: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Cc: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Maaz Mombasawala &lt;mombasawalam@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211215184147.3688785-2-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 15 Dec 2021 18:41:46 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>8afa13a0 - drm/vmwgfx: Implement DRIVER_GEM</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#8afa13a0</link>
        <description>drm/vmwgfx: Implement DRIVER_GEMThis is initial change adding support for DRIVER_GEM to vmwgfx. vmwgfxwas written before GEM and has always used TTM. Over the years theTTM buffers started inherting from GEM objects but vmwgfx neverimplemented GEM making it quite awkward. We were directly settingvariables in GEM objects to not make DRM crash.This change brings vmwgfx inline with other DRM drivers and allows usto use a lot of DRM helpers which have depended on drivers with GEMsupport.Due to historical reasons vmwgfx splits the idea of a buffer and surfacewhich makes it a littly tricky since either one can be used in mostof our ioctl&apos;s which take user space handles. For now our BO&apos;s areGEM objects and our surfaces are opaque objects which are backed byGEM objects. In the future I&apos;d like to combine those into a singleBO but we don&apos;t want to break any of our existing ioctl&apos;s so it willtake time to do it in a non-destructive way.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211206172620.3139754-5-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Mon, 06 Dec 2021 17:26:12 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>8aadeb8a - drm/vmwgfx: Remove the dedicated memory accounting</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#8aadeb8a</link>
        <description>drm/vmwgfx: Remove the dedicated memory accountingvmwgfx shared very elaborate memory accounting with ttm. It was movedfrom ttm to vmwgfx in changef07069da6b4c (&quot;drm/ttm: move memory accounting into vmwgfx v4&quot;)but because of complexity it was hard to maintain. Some parts of the codeweren&apos;t freeing memory correctly and  some were missing accounting alltogether. While those would be fairly easy to fix the fundamental reasonfor memory accounting in the driver was the ability to invoke shrinkerwhich is part of TTM code as well (with support for unified memoryhopefully coming soon).That meant that vmwgfx had a lot of code that was either unused orduplicating code from TTM. Removing this code also prevents excessivecalls to global swapout which were common during memory pressurebecause both vmwgfx and TTM would invoke the shrinker when memoryusage reached half of RAM.Fixes: f07069da6b4c (&quot;drm/ttm: move memory accounting into vmwgfx v4&quot;)Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211206172620.3139754-2-zack@kde.org

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Mon, 06 Dec 2021 17:26:09 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>f6be2326 - drm/vmwgfx: Introduce a new placement for MOB page tables</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#f6be2326</link>
        <description>drm/vmwgfx: Introduce a new placement for MOB page tablesFor larger (bigger than a page) and noncontiguous mobs we haveto create page tables that allow the host to find the memory.Those page tables just used regular system memory. Unfortunatelyin TTM those BO&apos;s are not allowed to be busy thus can&apos;t befenced and we have to fence those bo&apos;s  because we don&apos;t wantto destroy the page tables while the host is still executingthe command buffers which might be accessing them.To solve it we introduce a new placement VMW_PL_SYSTEM whichis very similar to TTM_PL_SYSTEM except that it allowsfencing. This fixes kernel oops&apos;es during unloading of the driver(and pci hot remove/add) which were caused by busy BO&apos;s inTTM_PL_SYSTEM being present in the delayed deletion list inTTM (TTM_PL_SYSTEM manager is destroyed before the delayeddeletions are executed)Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Cc: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Cc: Thomas Hellstr&#246;m &lt;thomas.hellstrom@linux.intel.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211105193845.258816-5-zackr@vmware.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Fri, 05 Nov 2021 19:38:45 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>2985c964 - drm/vmwgfx: Copy DRM hash-table code into driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#2985c964</link>
        <description>drm/vmwgfx: Copy DRM hash-table code into driverBesides some legacy code, vmwgfx is the only user of DRM&apos;s hash-table implementation. Copy the code into the driver, so that thecore code can be retired.No functional changes. However, the real solution for vmwgfx is touse Linux&apos; generic hash-table functions.v2:	* add TODO item for updating vmwgfx (Sam)Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Acked-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Acked-by: Alex Deucher &lt;alexander.deucher@amd.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20211129094841.22499-3-tzimmermann@suse.de

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Mon, 29 Nov 2021 09:48:40 +0000</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>d92223ea - drm/vmwgfx: Simplify devcaps code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#d92223ea</link>
        <description>drm/vmwgfx: Simplify devcaps codeMake devcaps code self-contained so that it&apos;s easier to cacheand operate on them.As the number of devcaps got bigger the code dealing with themgot more and more tricky. Lets create a central place to dealwith all the complexity. This lets us remove the lock we usedto require to deal with register write races because we onlyread the devcaps at initialization.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20210609172307.131929-2-zackr@vmware.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 09 Jun 2021 17:22:59 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>8211783f - drm/vmwgfx: Remove the reservation semaphore</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#8211783f</link>
        <description>drm/vmwgfx: Remove the reservation semaphoreNow since Christian reworked TTM to always keep objects on the LRUlist unless they are pinned we shouldn&apos;t need the reservationsemaphore. It makes the driver code a lot cleaner, especiallybecause it was a little hard to reason when and where thereservation semaphore needed to be held.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20210505035740.286923-5-zackr@vmware.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 05 May 2021 03:57:38 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>5dbf2fc5 - drm/vmwgfx: Make console emulation depend on DRM_FBDEV_EMULATION</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#5dbf2fc5</link>
        <description>drm/vmwgfx: Make console emulation depend on DRM_FBDEV_EMULATIONRespect DRM&apos;s kconfig setting for fbdev console emulation. If enabled,it will select all required config options. So remove them from vmwgfx&apos;sKconfig file.Signed-off-by: Thomas Zimmermann &lt;tzimmermann@suse.de&gt;Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20210415110040.23525-2-tzimmermann@suse.de

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Thu, 15 Apr 2021 11:00:37 +0000</pubDate>
        <dc:creator>Thomas Zimmermann &lt;tzimmermann@suse.de&gt;</dc:creator>
    </item>
<item>
        <title>f07069da - drm/ttm: move memory accounting into vmwgfx v4</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#f07069da</link>
        <description>drm/ttm: move memory accounting into vmwgfx v4This is just another feature which is only used by VMWGFX, so moveit into the driver instead.I&apos;ve tried to add the accounting sysfs file to the kobject of the drmminor, but I&apos;m not 100% sure if this works as expected.v2: fix typo in KFD and avoid 64bit dividev3: fix init order in VMWGFXv4: use pdev sysfs reference instead of drmSigned-off-by: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;Reviewed-by: Zack Rusin &lt;zackr@vmware.com&gt; (v3)Tested-by: Nirmoy Das &lt;nirmoy.das@amd.com&gt;Link: https://patchwork.freedesktop.org/patch/msgid/20210208133226.36955-2-christian.koenig@amd.com

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Tue, 17 Nov 2020 12:52:28 +0000</pubDate>
        <dc:creator>Christian K&#246;nig &lt;christian.koenig@amd.com&gt;</dc:creator>
    </item>
<item>
        <title>8426ed9c - drm/vmwgfx: Cleanup the cmd/fifo split</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#8426ed9c</link>
        <description>drm/vmwgfx: Cleanup the cmd/fifo splitLets try to cleanup the usage of the term FIFO which we used forboth our MMIO based cmd queue processing and for generalcommand processing which could have been using command buffersinterface. We&apos;re going to rename the functions which are processingcommands (and work either via MMIO or command buffers) as _cmd_and functions which operate on the MMIO based commands as FIFOto match the SVGA device naming.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/414044/?series=85516&amp;rev=2

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 18 Nov 2020 17:54:19 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>359dc60d - drm/vmwgfx: Remove the throttling code</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#359dc60d</link>
        <description>drm/vmwgfx: Remove the throttling codeThrottling was used before fencing to implement early vsyncsupport in the xorg state tracker a long time ago. The xorgstate tracker has been removed years ago and no one elsehas ever used throttling. It&apos;s time to remove this code,it hasn&apos;t been used or tested in years.Signed-off-by: Zack Rusin &lt;zackr@vmware.com&gt;Reviewed-by: Martin Krastev &lt;krastevm@vmware.com&gt;Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;Link: https://patchwork.freedesktop.org/patch/414042/?series=85516&amp;rev=2

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 11 Nov 2020 03:14:46 +0000</pubDate>
        <dc:creator>Zack Rusin &lt;zackr@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>7546f7ff - drm/vmwgfx: Introduce a huge page aligning TTM range manager</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#7546f7ff</link>
        <description>drm/vmwgfx: Introduce a huge page aligning TTM range managerUsing huge page-table entries requires that the physical address of thestart of a buffer object is huge page size aligned.Make a special version of the TTM range manager that accomplishes this,but falls back to a smaller page size alignment (PUD-&gt;PMD, PMD-&gt;NORMAL)to avoid eviction.If other drivers want to use it in the future, it can be made aTTM generic helper. Note that drivers can force eviction for a certainalignment by assigning the TTM GPU alignment correspondingly.Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;Cc: Michal Hocko &lt;mhocko@suse.com&gt;Cc: &quot;Matthew Wilcox (Oracle)&quot; &lt;willy@infradead.org&gt;Cc: &quot;Kirill A. Shutemov&quot; &lt;kirill.shutemov@linux.intel.com&gt;Cc: Ralph Campbell &lt;rcampbell@nvidia.com&gt;Cc: &quot;J&#233;r&#244;me Glisse&quot; &lt;jglisse@redhat.com&gt;Cc: &quot;Christian K&#246;nig&quot; &lt;christian.koenig@amd.com&gt;Cc: Dan Williams &lt;dan.j.williams@intel.com&gt;Signed-off-by: Thomas Hellstrom (VMware) &lt;thomas_os@shipmail.org&gt;Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;Acked-by: Christian K&#246;nig &lt;christian.koenig@amd.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Tue, 24 Mar 2020 17:50:12 +0000</pubDate>
        <dc:creator>Thomas Hellstrom (VMware) &lt;thomas_os@shipmail.org&gt;</dc:creator>
    </item>
<item>
        <title>e8bead9c - drm/vmwgfx: Add support for streamoutput with mob commands</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#e8bead9c</link>
        <description>drm/vmwgfx: Add support for streamoutput with mob commandsWith SM5 capability a new version of streamoutput is supported by devicewhich need backing mob and a new field. With this change the new commandis supported in command buffer.v2: Also track streamoutput context binding in binding manager.v3: Track only one streamoutput as only one can be set to context.v4: Fix comment typosSigned-off-by: Deepak Rawat &lt;drawat.floss@gmail.com&gt;Signed-off-by: Neha Bhende &lt;bhenden@vmware.com&gt;Reviewed-by: Thomas Hellstr&#246;m (VMware) &lt;thomas_os@shipmail.org&gt;Reviewed-by: Roland Scheidegger &lt;sroland@vmware.com&gt;Signed-off-by: Roland Scheidegger &lt;sroland@vmware.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Thu, 13 Dec 2018 22:04:31 +0000</pubDate>
        <dc:creator>Deepak Rawat &lt;drawat.floss@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b7468b15 - drm/vmwgfx: Implement an infrastructure for write-coherent resources</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#b7468b15</link>
        <description>drm/vmwgfx: Implement an infrastructure for write-coherent resourcesThis infrastructure will, for coherent resources, make sure thatfrom the user-space point of view, data written by the CPU is immediatelyautomatically available to the GPU at resource validation time.Cc: Andrew Morton &lt;akpm@linux-foundation.org&gt;Cc: Matthew Wilcox &lt;willy@infradead.org&gt;Cc: Will Deacon &lt;will.deacon@arm.com&gt;Cc: Peter Zijlstra &lt;peterz@infradead.org&gt;Cc: Rik van Riel &lt;riel@surriel.com&gt;Cc: Minchan Kim &lt;minchan@kernel.org&gt;Cc: Michal Hocko &lt;mhocko@suse.com&gt;Cc: Huang Ying &lt;ying.huang@intel.com&gt;Cc: J&#233;r&#244;me Glisse &lt;jglisse@redhat.com&gt;Cc: Kirill A. Shutemov &lt;kirill@shutemov.name&gt;Signed-off-by: Thomas Hellstrom &lt;thellstrom@vmware.com&gt;Reviewed-by: Deepak Rawat &lt;drawat@vmware.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Wed, 27 Mar 2019 09:56:08 +0000</pubDate>
        <dc:creator>Thomas Hellstrom &lt;thellstrom@vmware.com&gt;</dc:creator>
    </item>
<item>
        <title>3729fe2b - Revert &quot;Merge branch &apos;vmwgfx-next&apos; of git://people.freedesktop.org/~thomash/linux into drm-next&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/vmwgfx/Makefile#3729fe2b</link>
        <description>Revert &quot;Merge branch &apos;vmwgfx-next&apos; of git://people.freedesktop.org/~thomash/linux into drm-next&quot;This reverts commit 031e610a6a21448a63dff7a0416e5e206724caac, reversingchanges made to 52d2d44eee8091e740d0d275df1311fb8373c9a9.The mm changes in there we premature and not fully ack or reviewed by core mm folks,I dropped the ball by merging them via this tree, so lets take em all back out.Signed-off-by: Dave Airlie &lt;airlied@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/vmwgfx/Makefile</description>
        <pubDate>Mon, 15 Jul 2019 18:07:13 +0000</pubDate>
        <dc:creator>Dave Airlie &lt;airlied@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
