<?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>4c8cf318 - vhost: introduce vDPA-based backend</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#4c8cf318</link>
        <description>vhost: introduce vDPA-based backendThis patch introduces a vDPA-based vhost backend. This backend isbuilt on top of the same interface defined in virtio-vDPA and providesa generic vhost interface for userspace to accelerate the virtiodevices in guest.This backend is implemented as a vDPA device driver on top of the sameops used in virtio-vDPA. It will create char device entry namedvhost-vdpa-$index for userspace to use. Userspace can use vhost ioctlson top of this char device to setup the backend.Vhost ioctls are extended to make it type agnostic and behave like avirtio device, this help to eliminate type specific API like whatvhost_net/scsi/vsock did:- VHOST_VDPA_GET_DEVICE_ID: get the virtio device ID which is defined  by virtio specification to differ from different type of devices- VHOST_VDPA_GET_VRING_NUM: get the maximum size of virtqueue  supported by the vDPA device- VHSOT_VDPA_SET/GET_STATUS: set and get virtio status of vDPA device- VHOST_VDPA_SET/GET_CONFIG: access virtio config space- VHOST_VDPA_SET_VRING_ENABLE: enable a specific virtqueueFor memory mapping, IOTLB API is mandated for vhost-vDPA which meansuserspace drivers are required to useVHOST_IOTLB_UPDATE/VHOST_IOTLB_INVALIDATE to add or remove mapping fora specific userspace memory region.The vhost-vDPA API is designed to be type agnostic, but it allows netdevice only in current stage. Due to the lacking of control virtqueuesupport, some features were filter out by vhost-vdpa.We will enable more features and devices in the near future.Signed-off-by: Tiwei Bie &lt;tiwei.bie@intel.com&gt;Signed-off-by: Eugenio P&#233;rez &lt;eperezma@redhat.com&gt;Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;Link: https://lore.kernel.org/r/20200326140125.19794-8-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 26 Mar 2020 14:01:23 +0000</pubDate>
        <dc:creator>Tiwei Bie &lt;tiwei.bie@intel.com&gt;</dc:creator>
    </item>
<item>
        <title>0bbe3066 - vhost: factor out IOTLB</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#0bbe3066</link>
        <description>vhost: factor out IOTLBThis patch factors out IOTLB into a dedicated module in order to bereused by other modules like vringh. User may choose to enable theautomatic retiring by specifying VHOST_IOTLB_FLAG_RETIRE flag to fitfor the case of vhost device IOTLB implementation.Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;Link: https://lore.kernel.org/r/20200326140125.19794-4-jasowang@redhat.comSigned-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 26 Mar 2020 14:01:19 +0000</pubDate>
        <dc:creator>Jason Wang &lt;jasowang@redhat.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/vhost/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/vhost/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>304ba62f - VSOCK: Add Makefile and Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#304ba62f</link>
        <description>VSOCK: Add Makefile and KconfigEnable virtio-vsock and vhost-vsock.Signed-off-by: Asias He &lt;asias@redhat.com&gt;Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 28 Jul 2016 14:36:35 +0000</pubDate>
        <dc:creator>Asias He &lt;asias@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>8ac2837c - Revert &quot;Merge branch &apos;vsock-virtio&apos;&quot;</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#8ac2837c</link>
        <description>Revert &quot;Merge branch &apos;vsock-virtio&apos;&quot;This reverts commit 0d76d6e8b2507983a2cae4c09880798079007421 and mergecommit c402293bd76fbc93e52ef8c0947ab81eea3ae019, reversing changes madeto c89359a42e2a49656451569c382eed63e781153c.The virtio-vsock device specification is not finalized yet.  MichaelTsirkin voiced concerned about merging this code when the hardwareinterface (and possibly the userspace interface) could still change.Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Wed, 09 Dec 2015 02:51:12 +0000</pubDate>
        <dc:creator>Stefan Hajnoczi &lt;stefanha@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>8a2a2029 - VSOCK: Add Makefile and Kconfig</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#8a2a2029</link>
        <description>VSOCK: Add Makefile and KconfigEnable virtio-vsock and vhost-vsock.Signed-off-by: Asias He &lt;asias@redhat.com&gt;Signed-off-by: Stefan Hajnoczi &lt;stefanha@redhat.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Wed, 02 Dec 2015 06:44:03 +0000</pubDate>
        <dc:creator>Asias He &lt;asias@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>6ac1afbf - vhost: Make vhost a separate module</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#6ac1afbf</link>
        <description>vhost: Make vhost a separate moduleCurrently, vhost-net and vhost-scsi are sharing the vhost core code.However, vhost-scsi shares the code by including the vhost.c filedirectly.Making vhost a separate module makes it is easier to share code withother vhost devices.Signed-off-by: Asias He &lt;asias@redhat.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Mon, 06 May 2013 08:38:21 +0000</pubDate>
        <dc:creator>Asias He &lt;asias@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>181c04a3 - vhost_scsi: module rename</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#181c04a3</link>
        <description>vhost_scsi: module renameRename module and update Kconfig and Makefile.Add alias for compatibility with old userspacescripts if any.Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Reviewed-by: Asias He &lt;asias@redhat.com&gt;Acked-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 02 May 2013 00:52:59 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>eb62b74e - vhost: src file renames</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#eb62b74e</link>
        <description>vhost: src file renamesMove tcm_vhost.c -&gt; scsi.cSigned-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Reviewed-by: Asias He &lt;asias@redhat.com&gt;Acked-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 02 May 2013 00:37:38 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
<item>
        <title>f87d0fbb - vringh: host-side implementation of virtio rings.</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#f87d0fbb</link>
        <description>vringh: host-side implementation of virtio rings.Getting use of virtio rings correct is tricky, and a recent patch sawan implementation of in-kernel rings (as separate from userspace).This abstracts the business of dealing with the virtio ring layoutfrom the access (userspace or direct); to do this, we use functionpointers, which gcc inlines correctly.Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Wed, 20 Mar 2013 03:20:14 +0000</pubDate>
        <dc:creator>Rusty Russell &lt;rusty@rustcorp.com.au&gt;</dc:creator>
    </item>
<item>
        <title>057cbf49 - tcm_vhost: Initial merge for vhost level target fabric driver</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#057cbf49</link>
        <description>tcm_vhost: Initial merge for vhost level target fabric driverThis patch adds the initial code for tcm_vhost, a Vhost level TCMfabric driver for virtio SCSI initiators into KVM guest.This code is currently up and running on v3.5-rc2 host+guestfrom target-pending/for-next-merge.Using tcm_vhost requires Zhi&apos;s -&gt; Stefan -&gt; nab&apos;s qemu vhost-scsi tree here:  http://git.kernel.org/?p=virt/kvm/nab/qemu-kvm.git;a=shortlog;h=refs/heads/vhost-scsi--Changelog v4 -&gt; v5:  Expose ABI version via VHOST_SCSI_GET_ABI_VERSION + use Rev 0 as  starting point for v3.6-rc code (Stefan + ALiguori + nab)  Convert vhost_scsi_handle_vq() to vq_err() (nab + MST)  Minor style fixes from checkpatch (nab)Changelog v3 -&gt; v4:  Rename vhost_vring_target -&gt; vhost_scsi_target (mst + nab)  Use TRANSPORT_IQN_LEN in vhost_scsi_target-&gt;vhost_wwpn[] def (nab)  Move back to drivers/vhost/, and just use drivers/vhost/Kconfig.tcm (mst)  Move TCM_VHOST related ioctl defines from include/linux/vhost.h -&gt;  drivers/vhost/tcm_vhost.h as requested by MST (nab)  Move Kbuild.tcm include from drivers/staging -&gt; drivers/vhost/, and  just use &apos;if STAGING&apos; around &apos;source drivers/vhost/Kbuild.tcm&apos;Changelog v2 -&gt; v3:  Unlock on error in tcm_vhost_drop_nexus() (DanC)  Fix strlen() doesn&apos;t count the terminator (DanC)  Call kfree() on an error path (DanC)  Convert tcm_vhost_write_pending to use target_execute_cmd (hch + nab)  Fix another strlen() off by one in tcm_vhost_make_tport (DanC)  Add option under drivers/staging/Kconfig, and move to drivers/vhost/tcm/  as requested by MST (nab)Changelog v1 -&gt; v2:  Fix tv_cmd completion -&gt; release SGL memory leak (nab)  Fix sparse warnings for static variable usage ((Fengguang Wu)  Fix sparse warnings for min() typing + printk format specs (Fengguang Wu)  Convert to cmwq submission for I/O dispatch (nab + hch)Changelog v0 -&gt; v1:  Merge into single source + header file, and move to drivers/vhost/Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Cc: Stefan Hajnoczi &lt;stefanha@linux.vnet.ibm.com&gt;Cc: Anthony Liguori &lt;aliguori@us.ibm.com&gt;Cc: Zhi Yong Wu &lt;wuzhy@cn.ibm.com&gt;Cc: Paolo Bonzini &lt;pbonzini@redhat.com&gt;Cc: Christoph Hellwig &lt;hch@lst.de&gt;Cc: Hannes Reinecke &lt;hare@suse.de&gt;Cc: Jens Axboe &lt;axboe@kernel.dk&gt;Signed-off-by: Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Wed, 18 Jul 2012 21:31:32 +0000</pubDate>
        <dc:creator>Nicholas Bellinger &lt;nab@linux-iscsi.org&gt;</dc:creator>
    </item>
<item>
        <title>3a4d5c94 - vhost_net: a kernel-level virtio server</title>
        <link>http://172.16.0.5:8080/history/linux-6.15/drivers/vhost/Makefile#3a4d5c94</link>
        <description>vhost_net: a kernel-level virtio serverWhat it is: vhost net is a character device that can be used to reducethe number of system calls involved in virtio networking.Existing virtio net code is used in the guest without modification.There&apos;s similarity with vringfd, with some differences and reduced scope- uses eventfd for signalling- structures can be moved around in memory at any time (good for  migration, bug work-arounds in userspace)- write logging is supported (good for migration)- support memory table and not just an offset (needed for kvm)common virtio related code has been put in a separate file vhost.c andcan be made into a separate module if/when more backends appear.  I usedRusty&apos;s lguest.c as the source for developing this part : this suppliedme with witty comments I wouldn&apos;t be able to write myself.What it is not: vhost net is not a bus, and not a generic new systemcall. No assumptions are made on how guest performs hypercalls.Userspace hypervisors are supported as well as kvm.How it works: Basically, we connect virtio frontend (configured byuserspace) to a backend. The backend could be a network device, or a tapdevice.  Backend is also configured by userspace, including vlan/macetc.Status: This works for me, and I haven&apos;t see any crashes.Compared to userspace, people reported improved latency (as I save up to4 system calls per packet), as well as better bandwidth and CPUutilization.Features that I plan to look at in the future:- mergeable buffers- zero copy- scalability tuning: figure out the best threading model to useNote on RCU usage (this is also documented in vhost.h, nearprivate_pointer which is the value protected by this variant of RCU):what is happening is that the rcu_dereference() is being used in aworkqueue item.  The role of rcu_read_lock() is taken on by the start ofexecution of the workqueue item, of rcu_read_unlock() by the end ofexecution of the workqueue item, and of synchronize_rcu() byflush_workqueue()/flush_work(). In the future we might need to applysome gcc attribute or sparse annotation to the function passed toINIT_WORK(). Paul&apos;s ack below is for this RCU usage.(Includes fixes by Alan Cox &lt;alan@linux.intel.com&gt;,David L Stevens &lt;dlstevens@us.ibm.com&gt;,Chris Wright &lt;chrisw@redhat.com&gt;)Acked-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;Acked-by: Arnd Bergmann &lt;arnd@arndb.de&gt;Acked-by: &quot;Paul E. McKenney&quot; &lt;paulmck@linux.vnet.ibm.com&gt;Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;

            List of files:
            /linux-6.15/drivers/vhost/Makefile</description>
        <pubDate>Thu, 14 Jan 2010 06:17:27 +0000</pubDate>
        <dc:creator>Michael S. Tsirkin &lt;mst@redhat.com&gt;</dc:creator>
    </item>
</channel>
</rss>
