<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/tools/virtio, branch v4.11</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/
</subtitle>
<id>https://git.shady.money/linux/atom?h=v4.11</id>
<link rel='self' href='https://git.shady.money/linux/atom?h=v4.11'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/'/>
<updated>2017-01-19T21:46:32Z</updated>
<entry>
<title>tools/virtio/ringtest: tweaks for s390</title>
<updated>2017-01-19T21:46:32Z</updated>
<author>
<name>Halil Pasic</name>
<email>pasic@linux.vnet.ibm.com</email>
</author>
<published>2016-09-02T15:59:36Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=47a4c49af6cc1982ce613c8ee79aab459d04c44c'/>
<id>urn:sha1:47a4c49af6cc1982ce613c8ee79aab459d04c44c</id>
<content type='text'>
Make ringtest work on s390 too.

Signed-off-by: Halil Pasic &lt;pasic@linux.vnet.ibm.com&gt;
Acked-by: Sascha Silbe &lt;silbe@linux.vnet.ibm.com&gt;
Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;
</content>
</entry>
<entry>
<title>tools/virtio/ringtest: fix run-on-all.sh for offline cpus</title>
<updated>2017-01-19T21:46:31Z</updated>
<author>
<name>Halil Pasic</name>
<email>pasic@linux.vnet.ibm.com</email>
</author>
<published>2016-08-29T16:25:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=21f5eda9b8671744539c8295b9df62991fffb2ce'/>
<id>urn:sha1:21f5eda9b8671744539c8295b9df62991fffb2ce</id>
<content type='text'>
Since ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work
without /dev/cpu") run-on-all.sh uses seq 0 $HOST_AFFINITY as the list
of ids of the CPUs to run the command on (assuming ids of online CPUs
are consecutive and start from 0), where $HOST_AFFINITY is the highest
CPU id in the system previously determined using lscpu.  This can fail
on systems with offline CPUs.

Instead let's use lscpu to determine the list of online CPUs.

Signed-off-by: Halil Pasic &lt;pasic@linux.vnet.ibm.com&gt;
Fixes: ef1b144d ("tools/virtio/ringtest: fix run-on-all.sh to work without
/dev/cpu")
Reviewed-by: Sascha Silbe &lt;silbe@linux.vnet.ibm.com&gt;
Signed-off-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;
</content>
</entry>
<entry>
<title>tools/virtio: use {READ,WRITE}_ONCE() in uaccess.h</title>
<updated>2016-12-15T22:13:37Z</updated>
<author>
<name>Mark Rutland</name>
<email>mark.rutland@arm.com</email>
</author>
<published>2016-11-24T10:25:14Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=ea9156fb3b71d9f7e383253eaff9dd7498b23276'/>
<id>urn:sha1:ea9156fb3b71d9f7e383253eaff9dd7498b23276</id>
<content type='text'>
As a step towards killing off ACCESS_ONCE, use {READ,WRITE}_ONCE() for the
virtio tools uaccess primitives, pulling these in from &lt;linux/compiler.h&gt;.

With this done, we can kill off the now-unused ACCESS_ONCE() definition.

Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;
Cc: Jason Wang &lt;jasowang@redhat.com&gt;
Cc: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Cc: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Reviewed-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;
Reviewed-by: Jason Wang &lt;jasowang@redhat.com&gt;
</content>
</entry>
<entry>
<title>tools/virtio: fix READ_ONCE()</title>
<updated>2016-12-15T22:13:36Z</updated>
<author>
<name>Mark Rutland</name>
<email>mark.rutland@arm.com</email>
</author>
<published>2016-11-24T10:25:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=5da889c795b1fbefc9d8f058b54717ab8ab17891'/>
<id>urn:sha1:5da889c795b1fbefc9d8f058b54717ab8ab17891</id>
<content type='text'>
The virtio tools implementation of READ_ONCE() has a single parameter called
'var', but erroneously refers to 'val' for its cast, and thus won't work unless
there's a variable of the correct type that happens to be called 'var'.

Fix this with s/var/val/, making READ_ONCE() work as expected regardless.

Fixes: a7c490333df3cff5 ("tools/virtio: use virt_xxx barriers")
Signed-off-by: Mark Rutland &lt;mark.rutland@arm.com&gt;
Cc: Jason Wang &lt;jasowang@redhat.com&gt;
Cc: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Cc: linux-kernel@vger.kernel.org
Cc: virtualization@lists.linux-foundation.org
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Reviewed-by: Cornelia Huck &lt;cornelia.huck@de.ibm.com&gt;
Reviewed-by: Jason Wang &lt;jasowang@redhat.com&gt;
</content>
</entry>
<entry>
<title>ringtest: poll for new buffers once before updating event index</title>
<updated>2016-10-30T22:21:43Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2016-10-06T09:39:12Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=948a8ac2964f39161ebf832dea0aa1ced90101bb'/>
<id>urn:sha1:948a8ac2964f39161ebf832dea0aa1ced90101bb</id>
<content type='text'>
Updating the event index has a memory barrier and causes more work
on the other side to actually signal the event.  It is unnecessary
if a new buffer has already appeared on the ring, so poll once before
doing the update.

The effect of this on the 0.9 ring implementation is pretty much
invisible, but on the new-style ring it provides a consistent 3%
performance improvement.

Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>ringtest: commonize implementation of poll_avail/poll_used</title>
<updated>2016-10-30T22:21:43Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2016-10-06T09:39:11Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=d3c3589b8b3cd4fabf4cd137facb42a7fb36bd7f'/>
<id>urn:sha1:d3c3589b8b3cd4fabf4cd137facb42a7fb36bd7f</id>
<content type='text'>
Provide new primitives used_empty/avail_empty and
build poll_avail/poll_used on top of it.

Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>ringtest: use link-time optimization</title>
<updated>2016-10-30T22:21:42Z</updated>
<author>
<name>Paolo Bonzini</name>
<email>pbonzini@redhat.com</email>
</author>
<published>2016-10-06T09:39:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=44d65ea1615099ae252407f2554338d450cfdb1c'/>
<id>urn:sha1:44d65ea1615099ae252407f2554338d450cfdb1c</id>
<content type='text'>
By using -flto and -fwhole-program, all functions from the ring implementation
can be treated as static and possibly inlined.  Force this to happen through
the GCC flatten attribute.

Signed-off-by: Paolo Bonzini &lt;pbonzini@redhat.com&gt;
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>tools/virtio: add dma stubs</title>
<updated>2016-08-15T02:05:51Z</updated>
<author>
<name>Michael S. Tsirkin</name>
<email>mst@redhat.com</email>
</author>
<published>2016-08-15T01:50:55Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=6be3ffaa0e15c64f560904b025f5c50bef5886f9'/>
<id>urn:sha1:6be3ffaa0e15c64f560904b025f5c50bef5886f9</id>
<content type='text'>
Fixes build after recent IOMMU-related changes,
mustly by adding more stubs.

Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>ringtest: test build fix</title>
<updated>2016-08-15T02:01:23Z</updated>
<author>
<name>Michael S. Tsirkin</name>
<email>mst@redhat.com</email>
</author>
<published>2016-08-14T20:44:21Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=52012619e5a2ca0491426c3712fb9054692d4a3c'/>
<id>urn:sha1:52012619e5a2ca0491426c3712fb9054692d4a3c</id>
<content type='text'>
Recent changes to ptr_ring broke the ringtest
which lacks a likely() stub. Fix it up.

Fixes: 982fb490c298896d15e9323a882f34a57c11ff56
	("ptr_ring: support zero length ring")
Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
</content>
</entry>
<entry>
<title>ptr_ring: support resizing multiple queues</title>
<updated>2016-07-01T09:32:17Z</updated>
<author>
<name>Michael S. Tsirkin</name>
<email>mst@redhat.com</email>
</author>
<published>2016-06-30T06:45:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/linux/commit/?id=59e6ae53248a72d83cec77dd704b6990b2394479'/>
<id>urn:sha1:59e6ae53248a72d83cec77dd704b6990b2394479</id>
<content type='text'>
Sometimes, we need support resizing multiple queues at once. This is
because it was not easy to recover to recover from a partial failure
of multiple queues resizing.

Signed-off-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Jason Wang &lt;jasowang@redhat.com&gt;
Signed-off-by: David S. Miller &lt;davem@davemloft.net&gt;
</content>
</entry>
</feed>
