<?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>cba619cb - drm/i915/gvt: merge gvt.c into kvmgvt.c</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#cba619cb</link>
        <description>drm/i915/gvt: merge gvt.c into kvmgvt.cThe code in both files is deeply interconnected, so merge it andkeep a bunch of structures and functions static.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Link: http://patchwork.freedesktop.org/patch/msgid/20220411141403.86980-30-hch@lst.deReviewed-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Reviewed-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Mon, 11 Apr 2022 14:13:58 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>8b750bf7 - drm/i915/gvt: move the gvt code into kvmgt.ko</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#8b750bf7</link>
        <description>drm/i915/gvt: move the gvt code into kvmgt.koInstead of having an option to build the gvt code into the main i915module, just move it into the kvmgt.ko module.  This only requiresa new struct with three entries that the KVMGT modules needs to registerwith the main i915 module, and a proper list of GVT-enabled devicesinstead of global device pointer.Signed-off-by: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Link: http://patchwork.freedesktop.org/patch/msgid/20220411141403.86980-7-hch@lst.deReviewed-by: Jason Gunthorpe &lt;jgg@nvidia.com&gt;Reviewed-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Mon, 11 Apr 2022 14:13:35 +0000</pubDate>
        <dc:creator>Christoph Hellwig &lt;hch@lst.de&gt;</dc:creator>
    </item>
<item>
        <title>7f0cf301 - drm/i915/gvt: better align the Makefile with i915 Makefile</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#7f0cf301</link>
        <description>drm/i915/gvt: better align the Makefile with i915 MakefileDrop extra ccflags, drop extra intermediate variables, list object filesone per line alphabetically.Cc: Zhi Wang &lt;zhi.wang.linux@gmail.com&gt;Cc: Christoph Hellwig &lt;hch@lst.de&gt;Signed-off-by: Jani Nikula &lt;jani.nikula@intel.com&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Link: http://patchwork.freedesktop.org/patch/msgid/8bc0895376c077156a671e24ac6a5c75b7db4c9c.1649852517.git.jani.nikula@intel.comReviewed-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Reviewed-by: Christoph Hellwig &lt;hch@lst.de&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Wed, 13 Apr 2022 12:25:39 +0000</pubDate>
        <dc:creator>Jani Nikula &lt;jani.nikula@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>43068cb7 - drm: prefix header search paths with $(srctree)/</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#43068cb7</link>
        <description>drm: prefix header search paths with $(srctree)/Currently, the Kbuild core manipulates header search paths in a crazyway [1].To fix this mess, I want all Makefiles to add explicit $(srctree)/ tothe search paths in the srctree. Some Makefiles are already written inthat way, but not all. The goal of this work is to make the notationconsistent, and finally get rid of the gross hacks.Having whitespaces after -I does not matter since commit 48f6e3cf5bc6(&quot;kbuild: do not drop -I without parameter&quot;).[1]: https://patchwork.kernel.org/patch/9632347/Signed-off-by: Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;Reviewed-by: Sam Ravnborg &lt;sam@ravnborg.org&gt;Reviewed-by: James Qian Wang (Arm Technology China) &lt;james.qian.wang@arm.com&gt;Acked-by: Liviu Dudau &lt;liviu.dudau@arm.com&gt;Signed-off-by: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Link: https://patchwork.freedesktop.org/patch/msgid/1553859161-2628-1-git-send-email-yamada.masahiro@socionext.com

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Fri, 29 Mar 2019 11:32:41 +0000</pubDate>
        <dc:creator>Masahiro Yamada &lt;yamada.masahiro@socionext.com&gt;</dc:creator>
    </item>
<item>
        <title>9bdb0734 - drm/i915/gvt: Change KVMGT as self load module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#9bdb0734</link>
        <description>drm/i915/gvt: Change KVMGT as self load moduleThis trys to make &apos;kvmgt&apos; module as self loadable instead of loadingby i915/gvt device model. So hypervisor specific module could bestand-alone, e.g only after loading hypervisor specific module, GVTfeature could be enabled via specific hypervisor interface, e.g VFIO/mdev.So this trys to use hypervisor module register/unregister interfacefor that. Hypervisor module needs to take care of module referenceitself when working for hypervisor interface, e.g for VFIO/mdev,hypervisor module would reference counting mdev when open and release.This makes &apos;kvmgt&apos; module really split from GVT device model. Userneeds to load &apos;kvmgt&apos; to enable VFIO/mdev interface.v6:- remove unused variablev5:- put module reference in register error pathv4:- fix checkpatch warningv3:- Fix module reference handling for device open and release. Unused  mdev devices would be cleaned up in device unregister when module unload.v2:- Fix kvmgt order after i915 for built-in caseCc: &quot;Yuan, Hang&quot; &lt;hang.yuan@intel.com&gt;Cc: Alex Williamson &lt;alex.williamson@redhat.com&gt;Cc: &quot;He, Min&quot; &lt;min.he@intel.com&gt;Reviewed-by: Yuan, Hang &lt;hang.yuan@intel.com&gt;Acked-by: Joonas Lahtinen &lt;joonas.lahtinen@linux.intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Fri, 07 Dec 2018 08:16:53 +0000</pubDate>
        <dc:creator>Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e502a2af - drm/i915/gvt: Provide generic page_track infrastructure for write-protected page</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#e502a2af</link>
        <description>drm/i915/gvt: Provide generic page_track infrastructure for write-protected pageThis patch provide generic page_track infrastructure for write-protectedguest page. The old page_track logic gets rewrote and now stays in a newstandalone page_track.c. This page track infrastructure can be both usedby vGUC and GTT shadowing.The important change is that it uses radix tree instead of hash table.We don&apos;t have a predictable number of pages that will be tracked.Here is some performance data (duration in us) of looking up a element:Before: (aka. intel_vgpu_find_tracked_page) 0.091 0.089 0.090 ... 0.093 0.091 0.087 ... 0.292 0.285 0.292 0.291After: (aka. intel_vgpu_find_page_track) 0.104 0.105 0.100 0.102 0.102 0.100 ... 0.101 0.101 0.105 0.105The hash table has good performance at beginning, but turns bad withmore pages being tracked even no 3D applications are running. Asexpected, radix tree has stable duration and very quick.The overall benchmark (tested with Heaven Benchmark) marginally improvedsince this is not the bottleneck. What we benefit more from this changeis scalability.Signed-off-by: Changbin Du &lt;changbin.du@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Tue, 30 Jan 2018 11:19:53 +0000</pubDate>
        <dc:creator>Changbin Du &lt;changbin.du@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>1aec75ee - drm/i915/gvt: Rename file render.{c, h} to mmio_context.{c, h}</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#1aec75ee</link>
        <description>drm/i915/gvt: Rename file render.{c, h} to mmio_context.{c, h}Rename the files to reflect their real role - to switch the mmio context ofeach vGPU engine.v2: update Makefile.Signed-off-by: Changbin Du &lt;changbin.du@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Fri, 08 Dec 2017 06:56:23 +0000</pubDate>
        <dc:creator>Changbin Du &lt;changbin.du@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e546e281 - drm/i915/gvt: Dmabuf support for GVT-g</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#e546e281</link>
        <description>drm/i915/gvt: Dmabuf support for GVT-gThis patch introduces a guest&apos;s framebuffer sharing mechanism based ondma-buf subsystem. With this sharing mechanism, guest&apos;s framebuffer canbe shared between guest VM and host.v17:- modify VFIO_DEVICE_GET_GFX_DMABUF interface. (Alex)v16:- add x_hot and y_hot. (Gerd)- add flag validation for VFIO_DEVICE_GET_GFX_DMABUF. (Alex)- rebase 4.14.0-rc6.v15:- add VFIO_DEVICE_GET_GFX_DMABUF ABI. (Gerd)- add intel_vgpu_dmabuf_cleanup() to clean up the vGPU&apos;s dmabuf. (Gerd)v14:- add PROBE, DMABUF and REGION flags. (Alex)v12:- refine the lifecycle of dmabuf.v9:- remove dma-buf management. (Alex)- track the dma-buf create and release in kernel mode. (Gerd) (Daniel)v8:- refine the dma-buf ioctl definition.(Alex)- add a lock to protect the dmabuf list. (Alex)v7:- release dma-buf related allocations in dma-buf&apos;s associated release  function. (Alex)- refine ioctl interface for querying plane info or create dma-buf.  (Alex)v6:- align the dma-buf life cycle with the vfio device. (Alex)- add the dma-buf related operations in a separate patch. (Gerd)- i915 related changes. (Chris)v5:- fix bug while checking whether the gem obj is gvt&apos;s dma-buf when user  change caching mode or domains. Add a helper function to do it.  (Xiaoguang)- add definition for the query plane and create dma-buf. (Xiaoguang)v4:- fix bug while checking whether the gem obj is gvt&apos;s dma-buf when set  caching mode or doamins. (Xiaoguang)v3:- declare a new flag I915_GEM_OBJECT_IS_GVT_DMABUF in drm_i915_gem_object  to represent the gem obj for gvt&apos;s dma-buf. The tiling mode, caching  mode and domains can not be changed for this kind of gem object. (Alex)- change dma-buf related information to be more generic. So other vendor  can use the same interface. (Alex)v2:- create a management fd for dma-buf operations. (Alex)- alloc gem object&apos;s backing storage in gem obj&apos;s get_pages() callback.  (Chris)Signed-off-by: Tina Zhang &lt;tina.zhang@intel.com&gt;Cc: Alex Williamson &lt;alex.williamson@redhat.com&gt;Cc: Chris Wilson &lt;chris@chris-wilson.co.uk&gt;Cc: Daniel Vetter &lt;daniel.vetter@ffwll.ch&gt;Cc: Gerd Hoffmann &lt;kraxel@redhat.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Thu, 23 Nov 2017 08:26:36 +0000</pubDate>
        <dc:creator>Tina Zhang &lt;tina.zhang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>9f31d106 - drm/i915/gvt: Add framebuffer decoder support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#9f31d106</link>
        <description>drm/i915/gvt: Add framebuffer decoder supportThis patch is to introduce the framebuffer decoder which can decode guestOS&apos;s framebuffer information, including primary, cursor and sprite plane.v16:- rebase to 4.14.0-rc6.v14:- refine pixel format table. (Zhenyu)v9:- move drm format change to a separate patch. (Xiaoguang)v8:- fix a bug in decoding primary plane. (Tina)v7:- refine framebuffer decoder code. (Zhenyu)Signed-off-by: Tina Zhang &lt;tina.zhang@intel.com&gt;Cc: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Thu, 23 Nov 2017 08:26:32 +0000</pubDate>
        <dc:creator>Tina Zhang &lt;tina.zhang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>bc7b0be3 - drm/i915/gvt: Add basic debugfs infrastructure</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#bc7b0be3</link>
        <description>drm/i915/gvt: Add basic debugfs infrastructureWe need debugfs entry to expose some debug information of gvt and vGPUs.The first tool will be added is mmio-diff, which help to find thedifference values of host and vGPU mmio. It&apos;s useful for platformenabling.This patch just add a basic debugfs infrastructure, each vGPU has its ownsub-folder. Two simple attributes are created as a template..&#9500;&#9472;&#9472; num_tracked_mmio&#9500;&#9472;&#9472; vgpu1|   &#9492;&#9472;&#9472; active&#9492;&#9472;&#9472; vgpu2    &#9492;&#9472;&#9472; activeSigned-off-by: Changbin Du &lt;changbin.du@intel.com&gt;Reviewed-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Tue, 26 Sep 2017 08:19:13 +0000</pubDate>
        <dc:creator>Changbin Du &lt;changbin.du@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>b2441318 - License cleanup: add SPDX GPL-2.0 license identifier to files with no license</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#b2441318</link>
        <description>License cleanup: add SPDX GPL-2.0 license identifier to files with no licenseMany source files in the tree are missing licensing information, whichmakes it harder for compliance tools to determine the correct license.By default all files without license information are under the defaultlicense of the kernel, which is GPL version 2.Update the files which contain no license information with the &apos;GPL-2.0&apos;SPDX license identifier.  The SPDX identifier is a legally bindingshorthand, which can be used instead of the full boiler plate text.This patch is based on work done by Thomas Gleixner and Kate Stewart andPhilippe Ombredanne.How this work was done:Patches were generated and checked against linux-4.14-rc6 for a subset ofthe use cases: - file had no licensing information it it. - file was a */uapi/* one with no licensing information in it, - file was a */uapi/* one with existing licensing information,Further patches will be generated in subsequent months to fix up caseswhere non-standard license headers were used, and references to licensehad to be inferred by heuristics based on keywords.The analysis to determine which SPDX License Identifier to be applied toa file was done in a spreadsheet of side by side results from of theoutput of two independent scanners (ScanCode &amp; Windriver) producing SPDXtag:value files created by Philippe Ombredanne.  Philippe prepared thebase worksheet, and did an initial spot review of a few 1000 files.The 4.13 kernel was the starting point of the analysis with 60,537 filesassessed.  Kate Stewart did a file by file comparison of the scannerresults in the spreadsheet to determine which SPDX license identifier(s)to be applied to the file. She confirmed any determination that was notimmediately clear with lawyers working with the Linux Foundation.Criteria used to select files for SPDX license identifier tagging was: - Files considered eligible had to be source code files. - Make and config files were included as candidates if they contained &gt;5   lines of source - File already had some variant of a license header in it (even if &lt;5   lines).All documentation files were explicitly excluded.The following heuristics were used to determine which SPDX licenseidentifiers to apply. - when both scanners couldn&apos;t find any license traces, file was   considered to have no license information in it, and the top level   COPYING file license applied.   For non */uapi/* files that summary was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0                                              11139   and resulted in the first patch in this series.   If that file was a */uapi/* path one, it was &quot;GPL-2.0 WITH   Linux-syscall-note&quot; otherwise it was &quot;GPL-2.0&quot;.  Results of that was:   SPDX license identifier                            # files   ---------------------------------------------------|-------   GPL-2.0 WITH Linux-syscall-note                        930   and resulted in the second patch in this series. - if a file had some form of licensing information in it, and was one   of the */uapi/* ones, it was denoted with the Linux-syscall-note if   any GPL family license was found in the file or had no licensing in   it (per prior point).  Results summary:   SPDX license identifier                            # files   ---------------------------------------------------|------   GPL-2.0 WITH Linux-syscall-note                       270   GPL-2.0+ WITH Linux-syscall-note                      169   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-2-Clause)    21   ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)    17   LGPL-2.1+ WITH Linux-syscall-note                      15   GPL-1.0+ WITH Linux-syscall-note                       14   ((GPL-2.0+ WITH Linux-syscall-note) OR BSD-3-Clause)    5   LGPL-2.0+ WITH Linux-syscall-note                       4   LGPL-2.1 WITH Linux-syscall-note                        3   ((GPL-2.0 WITH Linux-syscall-note) OR MIT)              3   ((GPL-2.0 WITH Linux-syscall-note) AND MIT)             1   and that resulted in the third patch in this series. - when the two scanners agreed on the detected license(s), that became   the concluded license(s). - when there was disagreement between the two scanners (one detected a   license but the other didn&apos;t, or they both detected different   licenses) a manual inspection of the file occurred. - In most cases a manual inspection of the information in the file   resulted in a clear resolution of the license that should apply (and   which scanner probably needed to revisit its heuristics). - When it was not immediately clear, the license identifier was   confirmed with lawyers working with the Linux Foundation. - If there was any question as to the appropriate license identifier,   the file was flagged for further research and to be revisited later   in time.In total, over 70 hours of logged manual review was done on thespreadsheet to determine the SPDX license identifiers to apply to thesource files by Kate, Philippe, Thomas and, in some cases, confirmationby lawyers working with the Linux Foundation.Kate also obtained a third independent scan of the 4.13 code base fromFOSSology, and compared selected files where the other two scannersdisagreed against that SPDX file, to see if there was new insights.  TheWindriver scanner is based on an older version of FOSSology in part, sothey are related.Thomas did random spot checks in about 500 files from the spreadsheetsfor the uapi headers and agreed with SPDX license identifier in thefiles he inspected. For the non-uapi files Thomas did random spot checksin about 15000 files.In initial set of patches against 4.14-rc6, 3 files were found to havecopy/paste license identifier errors, and have been fixed to reflect thecorrect identifier.Additionally Philippe spent 10 hours this week doing a detailed manualinspection and review of the 12,461 patched files from the initial patchversion early this week with: - a full scancode scan run, collecting the matched texts, detected   license ids and scores - reviewing anything where there was a license detected (about 500+   files) to ensure that the applied SPDX license was correct - reviewing anything where there was no detection but the patch license   was not GPL-2.0 WITH Linux-syscall-note to ensure that the applied   SPDX license was correctThis produced a worksheet with 20 files needing minor correction.  Thisworksheet was then exported into 3 different .csv files for thedifferent types of files to be modified.These .csv files were then reviewed by Greg.  Thomas wrote a script toparse the csv files and add the proper SPDX tag to the file, in theformat that the file expected.  This script was further refined by Gregbased on the output to detect more types of files automatically and todistinguish between header and source .c files (which need differentcomment types.)  Finally Greg ran the script using the .csv files togenerate the patches.Reviewed-by: Kate Stewart &lt;kstewart@linuxfoundation.org&gt;Reviewed-by: Philippe Ombredanne &lt;pombredanne@nexb.com&gt;Reviewed-by: Thomas Gleixner &lt;tglx@linutronix.de&gt;Signed-off-by: Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Wed, 01 Nov 2017 14:07:57 +0000</pubDate>
        <dc:creator>Greg Kroah-Hartman &lt;gregkh@linuxfoundation.org&gt;</dc:creator>
    </item>
<item>
        <title>89009b77 - drm/i915/gvt: remove redundant -Wall</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#89009b77</link>
        <description>drm/i915/gvt: remove redundant -WallThis flag is already set in the top level Makefile of the kernel.Also, by having set CONFIG_DRM_I915_GVT, thereby appending -Wall toccflags, you undo all the -Wno-* cflags previously set in the Makevariable KBUILD_CFLAGS.For example:cc foo.c -Wall -Wno-format -Wallresets -Wformat.Signed-off-by: Nick Desaulniers &lt;nick.desaulniers@gmail.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Sun, 21 May 2017 07:15:27 +0000</pubDate>
        <dc:creator>Nick Desaulniers &lt;nick.desaulniers@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>659643f7 - drm/i915/gvt/kvmgt: add vfio/mdev support to KVMGT</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#659643f7</link>
        <description>drm/i915/gvt/kvmgt: add vfio/mdev support to KVMGTKVMGT leverages vfio/mdev to mediate device accesses from guest,this patch adds the vfio/mdev support, thereby completes thefunctionality. An intel_vgpu is presented as a mdev device,and full userspace API compatibility with vfio-pci is kept.An intel_vgpu_ops is provided to mdev framework, methods getcalled to create/remove a vgpu, to open/close it, and toaccess it.Signed-off-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Signed-off-by: Xiaoguang Chen &lt;xiaoguang.chen@intel.com&gt;Signed-off-by: Jike Song &lt;jike.song@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Thu, 08 Dec 2016 03:00:36 +0000</pubDate>
        <dc:creator>Jike Song &lt;jike.song@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>f30437c5 - drm/i915/gvt: add KVMGT support</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#f30437c5</link>
        <description>drm/i915/gvt: add KVMGT supportKVMGT is the MPT implementation based on VFIO/KVM. It providesa kvmgt_mpt ops to gvt for vGPU access mediation, e.g. tomediate and emulate the MMIO accesses, to inject interruptsto vGPU user, to intercept the GTT writing and replace it withDMA-able address, to write-protect guest PPGTT table forshadowing synchronization, etc. This patch provides the MPTimplementation for GVT, not yet functional due to theabsenceof mdev.It&apos;s built as kvmgt.ko, depends on vfio.ko, kvm.ko and mdev.ko,and being required by i915.ko. To not introduce hard dependencyin i915.ko, we used indirect symbol reference. But that meansusers have to include kvmgt.ko into init ramdisk if theiri915.ko is included.Signed-off-by: Kevin Tian &lt;kevin.tian@intel.com&gt;Signed-off-by: Xiaoguang Chen &lt;xiaoguang.chen@intel.com&gt;Signed-off-by: Jike Song &lt;jike.song@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Wed, 09 Nov 2016 12:30:59 +0000</pubDate>
        <dc:creator>Jike Song &lt;jike.song@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>be1da707 - drm/i915/gvt: vGPU command scanner</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#be1da707</link>
        <description>drm/i915/gvt: vGPU command scannerThis patch introduces a command scanner to scan guest command buffers.Signed-off-by: Yulei Zhang &lt;yulei.zhang@intel.com&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Tue, 03 May 2016 22:26:57 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>17865713 - drm/i915/gvt: vGPU context switch</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#17865713</link>
        <description>drm/i915/gvt: vGPU context switchAs different VM may configure different render MMIOs when executingworkload, to schedule workloads between different VM, the render MMIOshave to be switched.Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Sun, 01 May 2016 23:02:37 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>4b63960e - drm/i915/gvt: vGPU schedule policy framework</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#4b63960e</link>
        <description>drm/i915/gvt: vGPU schedule policy frameworkThis patch introduces a vGPU schedule policy framework, with a timer basedschedule policy module for nowSigned-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Sun, 01 May 2016 21:09:58 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>e4734057 - drm/i915/gvt: vGPU workload scheduler</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#e4734057</link>
        <description>drm/i915/gvt: vGPU workload schedulerThis patch introduces the vGPU workload scheduler routines.GVT workload scheduler is responsible for picking and executing GVT workloadfrom current scheduled vGPU. Before the workload is submitted to host i915,the guest execlist context will be shadowed in the host GVT shadow context.the instructions in guest ring buffer will be copied into GVT shadow ringbuffer. Then GVT-g workload scheduler will scan the instructions in guestring buffer and submit it to host i915.Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Sun, 01 May 2016 11:42:16 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>8453d674 - drm/i915/gvt: vGPU execlist virtualization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#8453d674</link>
        <description>drm/i915/gvt: vGPU execlist virtualizationThis patch introduces the vGPU execlist virtualization.Under virtulization environment, HW execlist interface are fully emulatedincluding virtual CSB emulation, virtual execlist emulation. The frameworkwill emulate the virtual CSB according to the guest workload running statusSigned-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Sun, 01 May 2016 06:48:25 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>04d348ae - drm/i915/gvt: vGPU display virtualization</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/gpu/drm/i915/gvt/Makefile#04d348ae</link>
        <description>drm/i915/gvt: vGPU display virtualizationThis patch introduces the GVT-g display virtualization.It consists a collection of display MMIO handlers, like power well registerhandler, pipe register handler, plane register handler, which will emulateall display MMIOs behavior to support virtual mode setting sequence forguest.Signed-off-by: Bing Niu &lt;bing.niu@intel.com&gt;Signed-off-by: Zhi Wang &lt;zhi.a.wang@intel.com&gt;Signed-off-by: Zhenyu Wang &lt;zhenyuw@linux.intel.com&gt;

            List of files:
            /linux-6.15/drivers/gpu/drm/i915/gvt/Makefile</description>
        <pubDate>Mon, 25 Apr 2016 22:28:56 +0000</pubDate>
        <dc:creator>Zhi Wang &lt;zhi.a.wang@intel.com&gt;</dc:creator>
    </item>
</channel>
</rss>
