<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/drivers/virtio, branch v3.16</title>
<subtitle>Linux kernel source tree</subtitle>
<id>https://git.amat.us/linux/atom/drivers/virtio?h=v3.16</id>
<link rel='self' href='https://git.amat.us/linux/atom/drivers/virtio?h=v3.16'/>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/'/>
<updated>2014-04-28T02:04:13Z</updated>
<entry>
<title>virtio: virtio_break_device() to mark all virtqueues broken.</title>
<updated>2014-04-28T02:04:13Z</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2014-04-28T01:45:08Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=e2dcdfe95c0bd67e37db6057edd9c4ee1f1c7b17'/>
<id>urn:sha1:e2dcdfe95c0bd67e37db6057edd9c4ee1f1c7b17</id>
<content type='text'>
Good for post-apocalyptic scenarios, like S/390 hotplug.

Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio: fail adding buffer on broken queues.</title>
<updated>2014-03-13T00:57:57Z</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2014-03-13T00:53:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=70670444c20a10717acdc1f4c1e420852995496d'/>
<id>urn:sha1:70670444c20a10717acdc1f4c1e420852995496d</id>
<content type='text'>
Heinz points out that adding buffers to a broken virtqueue (which
should "never happen") still works.  Failing allows drivers to detect
and complain about broken devices.

Now drivers are robust, we can add this extra check.

Reported-by: Heinz Graalfs &lt;graalfs@linux.vnet.ibm.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio_balloon: don't crash if virtqueue is broken.</title>
<updated>2014-03-13T00:57:56Z</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2014-03-13T00:53:40Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=4951cc9083147015338f61a187e072daf02dfd4e'/>
<id>urn:sha1:4951cc9083147015338f61a187e072daf02dfd4e</id>
<content type='text'>
A bad implementation of virtio might cause us to mark the virtqueue
broken: we'll dev_err() in that case, and the device is useless, but
let's not BUG().

Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio_balloon: don't softlockup on huge balloon changes.</title>
<updated>2014-03-13T00:57:55Z</updated>
<author>
<name>Rusty Russell</name>
<email>rusty@rustcorp.com.au</email>
</author>
<published>2014-03-13T00:53:38Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=1f74ef0f2d7d692fcd615621e0e734c3e7771413'/>
<id>urn:sha1:1f74ef0f2d7d692fcd615621e0e734c3e7771413</id>
<content type='text'>
When adding or removing 100G from a balloon:

    BUG: soft lockup - CPU#0 stuck for 22s! [vballoon:367]

We have a wait_event_interruptible(), but the condition is always true
(more ballooning to do) so we don't ever sleep.  We also have a
wait_event() for the host to ack, but that is also always true as QEMU
is synchronous for balloon operations.

Reported-by: Gopesh Kumar Chaudhary &lt;gopchaud@in.ibm.com&gt;
Cc: stable@kernel.org
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio: Use pci_enable_msix_exact() instead of pci_enable_msix()</title>
<updated>2014-03-13T00:57:54Z</updated>
<author>
<name>Alexander Gordeev</name>
<email>agordeev@redhat.com</email>
</author>
<published>2014-03-13T00:53:37Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=5e37f67063a14450f1fff3baee81efe7c146592a'/>
<id>urn:sha1:5e37f67063a14450f1fff3baee81efe7c146592a</id>
<content type='text'>
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range()  or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.

Signed-off-by: Alexander Gordeev &lt;agordeev@redhat.com&gt;
Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>tools/virtio: fix missing kmemleak_ignore symbol</title>
<updated>2014-03-13T00:53:25Z</updated>
<author>
<name>Joel Stanley</name>
<email>joel@jms.id.au</email>
</author>
<published>2014-02-13T04:33:46Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=6abb2dd92868927c1d680546b9d13f208373d517'/>
<id>urn:sha1:6abb2dd92868927c1d680546b9d13f208373d517</id>
<content type='text'>
In commit bb478d8b167 virtio_ring: plug kmemleak false positive,
kmemleak_ignore was introduced. This broke compilation of virtio_test:

  cc -g -O2 -Wall -I. -I ../../usr/include/ -Wno-pointer-sign
    -fno-strict-overflow -fno-strict-aliasing -fno-common -MMD
    -U_FORTIFY_SOURCE   -c -o virtio_ring.o ../../drivers/virtio/virtio_ring.c
  ../../drivers/virtio/virtio_ring.c: In function ‘vring_add_indirect’:
  ../../drivers/virtio/virtio_ring.c:177:2: warning: implicit declaration
  of function ‘kmemleak_ignore’ [-Wimplicit-function-declaration]
    kmemleak_ignore(desc);
    ^
  cc   virtio_test.o virtio_ring.o   -o virtio_test
  virtio_ring.o: In function `vring_add_indirect':
  tools/virtio/../../drivers/virtio/virtio_ring.c:177:
  undefined reference to `kmemleak_ignore'

Add a dummy header for tools/virtio, and add #incldue &lt;linux/kmemleak.h&gt;
to drivers/virtio/virtio_ring.c so it is picked up by the userspace
tools.

Signed-off-by: Joel Stanley &lt;joel@jms.id.au&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>Merge tag 'virtio-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux</title>
<updated>2014-01-23T06:24:35Z</updated>
<author>
<name>Linus Torvalds</name>
<email>torvalds@linux-foundation.org</email>
</author>
<published>2014-01-23T06:24:35Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=93b05cba8ed52a751da9c4c7da6c97bc514bec77'/>
<id>urn:sha1:93b05cba8ed52a751da9c4c7da6c97bc514bec77</id>
<content type='text'>
Pull virtio update from Rusty Russell:
 "A few simple fixes.  Quiet cycle"

* tag 'virtio-next-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/rusty/linux:
  drivers: virtio: Mark function virtballoon_migratepage() as static in virtio_balloon.c
  virtio-scsi: Fix hotcpu_notifier use-after-free with virtscsi_freeze
  virtio: pci: remove unnecessary pci_set_drvdata()
</content>
</entry>
<entry>
<title>drivers: virtio: Mark function virtballoon_migratepage() as static in virtio_balloon.c</title>
<updated>2014-01-15T23:52:28Z</updated>
<author>
<name>Rashika Kheria</name>
<email>rashika.kheria@gmail.com</email>
</author>
<published>2014-01-15T23:48:48Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=05c54de8c88c02bd0a44de8316d5e276b856632e'/>
<id>urn:sha1:05c54de8c88c02bd0a44de8316d5e276b856632e</id>
<content type='text'>
Mark the function virtballoon_migratepage() as static in
virtio_balloon.c because it is not used outside this file.

This eliminates the following warning in virtio_balloon.c:
drivers/virtio/virtio_balloon.c:372:5: warning: no previous prototype for ‘virtballoon_migratepage’ [-Wmissing-prototypes]

Signed-off-by: Rashika Kheria &lt;rashika.kheria@gmail.com&gt;
Reviewed-by: Josh Triplett &lt;josh@joshtriplett.org&gt;
Acked-by: Michael S. Tsirkin &lt;mst@redhat.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
<entry>
<title>virtio_balloon: update_balloon_size(): update correct field</title>
<updated>2013-12-05T02:42:39Z</updated>
<author>
<name>Luiz Capitulino</name>
<email>lcapitulino@redhat.com</email>
</author>
<published>2013-12-05T02:34:10Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=3459f11a8b16f40f9cde8e4281c2d5dd2ff1a732'/>
<id>urn:sha1:3459f11a8b16f40f9cde8e4281c2d5dd2ff1a732</id>
<content type='text'>
According to the virtio spec, the device configuration field
that should be updated after an inflation or deflation
operation is the 'actual' field, not the 'num_pages' one.

Commit 855e0c5288177bcb193f6f6316952d2490478e1c swapped them
in update_balloon_size(). Fix it.

Signed-off-by: Luiz Capitulino &lt;lcapitulino@redhat.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
Fixes: 855e0c5288177bcb193f6f6316952d2490478e1c
</content>
</entry>
<entry>
<title>virtio: pci: remove unnecessary pci_set_drvdata()</title>
<updated>2013-12-04T03:50:26Z</updated>
<author>
<name>Jingoo Han</name>
<email>jg1.han@samsung.com</email>
</author>
<published>2013-12-02T20:14:01Z</published>
<link rel='alternate' type='text/html' href='https://git.amat.us/linux/commit/?id=7d2dddda5c928f349a01f1d5ca8ee5e9d4283c7a'/>
<id>urn:sha1:7d2dddda5c928f349a01f1d5ca8ee5e9d4283c7a</id>
<content type='text'>
The driver core clears the driver data to NULL after device_release
or on probe failure. Thus, it is not needed to manually clear the
device driver data to NULL.

Signed-off-by: Jingoo Han &lt;jg1.han@samsung.com&gt;
Signed-off-by: Rusty Russell &lt;rusty@rustcorp.com.au&gt;
</content>
</entry>
</feed>
