Linux Virtualization Development

• Thread Index

• [PATCH 1/2] virtio-gpu/2d: add hardware spec include file
  • From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
• [PATCH 0/2] virtio-gpu: hardware specification
  • From: Gerd Hoffmann <kraxel@xxxxxxxxxx>
• Re: [PATCH 2/2] virtio-rng: fix stuck in catting hwrng attributes
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: Rusty away 18th September -- 11th October
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• blk-mq crash under KVM in multiqueue block code (with virtio-blk and ext4)
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH 2/2] virtio-rng: fix stuck in catting hwrng attributes
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2] virtio-rng cleanup: move some code out of mutex protection
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Rusty away 18th September -- 11th October
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• [PATCH 2/2] virtio-rng: fix stuck in catting hwrng attributes
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH 1/2] virtio-rng cleanup: move some code out of mutex protection
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH 0/2] fix stuck in catting hwrng attributes
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: RFC virtio-rng: fail to read sysfs of a busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH v3 2/2] virtio-rng: skip reading when we start to remove the device
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v3 1/2] virtio-rng: fix stuck of hot-unplugging busy device
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: RFC virtio-rng: fail to read sysfs of a busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH v2] virtio-rng: fix stuck of hot-unplugging busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH v3 2/2] virtio-rng: skip reading when we start to remove the device
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH v3 1/2] virtio-rng: fix stuck of hot-unplugging busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH v3 0/2] virtio-rng: fix hotunplug
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: RFC virtio-rng: fail to read sysfs of a busy device
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2] virtio-rng: fix stuck of hot-unplugging busy device
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Ming Lei <tom.leiming@xxxxxxxxx>
• RFC virtio-rng: fail to read sysfs of a busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• mutex
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH v2] virtio-rng: fix stuck of hot-unplugging busy device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH] virtio-rng: complete have_data completion in removing device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH] virtio: pci: Use SIMPLE_DEV_PM_OPS macro
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 3/3] virtio_ring: unify direct/indirect code paths.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH] virtio-rng: complete have_data completion in removing device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] virtio_blk: merge S/G list entries by default
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH] virtio_blk: merge S/G list entries by default
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH 0/3] virtio: simplify virtio_ring.
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH] VMXNET3: Check for map error in vmxnet3_set_mc
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
  • From: Jesper Dangaard Brouer <brouer@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxx>
• [WorldCIST'15]: Call for Workshops Proposals; Best papers published in ISI Journals
  • From: "ML" <marialemos72@xxxxxxxxx>
• Re: [PATCH 3/3] virtio_ring: unify direct/indirect code paths.
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH 3/3] virtio_ring: unify direct/indirect code paths.
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] virtio: pci: Use SIMPLE_DEV_PM_OPS macro
  • From: Jingoo Han <jg1.han@xxxxxxxxxxx>
• Re: [PATCH 1/1] add selftest for virtio-net v1.0
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH 1/1] add selftest for virtio-net v1.0
  • From: Hengjinxiao <hjxiaohust@xxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 3/3] virtio_ring: unify direct/indirect code paths.
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Setting up VHost without QEMU?
  • From: 가니스 <ganis@xxxxxxxxxx>
• Re: [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH 0/3] virtio: simplify virtio_ring.
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH 2/3] virtio_ring: assume sgs are always well-formed.
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH 3/3] virtio_ring: unify direct/indirect code paths.
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• [PATCH 1/3] virtio_net: pass well-formed sgs to virtqueue_add_*()
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• [PATCH] VMXNET3: Check for map error in vmxnet3_set_mc
  • From: Andy King <acking@xxxxxxxxxx>
• [no subject]
  • From: Andy King <acking@xxxxxxxxxx>
• Re: [PATCH] VMXNET3: Check for map error in vmxnet3_set_mc
  • From: Sergei Shtylyov <sergei.shtylyov@xxxxxxxxxxxxxxxxxx>
• [PATCH] VMXNET3: Check for map error in vmxnet3_set_mc
  • From: Andy King <acking@xxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• [PATCH v4 4/4] virtio_net: Stop doing DMA from the stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v4 3/4] virtio_net: Don't set the end flag on reusable sg entries
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v4 2/4] virtio_pci: Use the DMA API for virtqueues
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v4 1/4] virtio_ring: Support DMA APIs if requested
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v4 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] virtio_ring: Remove sg_next indirection
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH RFC] virtio-pci: share config interrupt between virtio devices
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH RFC] virtio-pci: share config interrupt between virtio devices
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH 1/3] virtio_ring: Remove sg_next indirection
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH RFC] virtio-pci: share config interrupt between virtio devices
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH RFC] virtio-pci: share config interrupt between virtio devices
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [PATCH 1/3] virtio_ring: Remove sg_next indirection
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 1/3] virtio_ring: Remove sg_next indirection
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH v3 0/5] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 5/5] virtio_ring: Remove sg_next indirection
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 4/5] virtio_net: Don't set the end flag on reusable sg entries
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 3/5] virtio_net: Stop doing DMA from the stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 2/5] virtio_pci: Use the DMA API for virtqueues
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 1/5] virtio_ring: Support DMA APIs if requested
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v3 0/5] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [virtio-dev] Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [virtio-dev] Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [virtio-dev] Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [virtio-dev] Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Gleb Natapov <gleb@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• [PATCH v2 4/4] virtio_net: Stop doing DMA from the stack
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v2 3/4] virtio_pci: Use the DMA API for virtqueues
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v2 2/4] virtio_ring: Support DMA APIs if requested
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v2 1/4] virtio_ring: Remove sg_next indirection
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH v2 0/4] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Benjamin Herrenschmidt <benh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: virtio DMA API?
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 3/3] virtio_pci: Use the DMA API for virtqueues
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [PATCH 2/3] virtio_ring: Use DMA APIs
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 2/3] virtio_ring: Use DMA APIs
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 3/3] virtio_pci: Use the DMA API for virtqueues
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [PATCH 3/3] virtio_pci: Use the DMA API for virtqueues
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• [PATCH 1/1] add selftest for virtio-net
  • From: Hengjinxiao <hjxiaohust@xxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: [PATCH 1/1] add selftest for virtio-net
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: virtio DMA API?
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: virtio DMA API?
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [3.16 stable PATCH v2 1/2] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Cornelia Huck <cornelia.huck@xxxxxxxxxx>
• Re: [PATCH 2/3] virtio_ring: Use DMA APIs
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: help? looking for limits on in-flight write operations for virtio-blk
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
• Re: [PATCH 1/1] add selftest for virtio-net
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• GET_RNG_SEED hypercall ABI? (Re: [PATCH v5 0/5] random,x86,kvm: Rework arch RNG seeds and get some from kvm)
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH 3/3] virtio_pci: Use the DMA API for virtqueues
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH 2/3] virtio_ring: Use DMA APIs
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH 1/3] virtio_ring: Remove sg_next indirection
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [PATCH 0/3] virtio: Clean up scatterlists and use the DMA API
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: help? looking for limits on in-flight write operations for virtio-blk
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
• Re: help? looking for limits on in-flight write operations for virtio-blk
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• help? looking for limits on in-flight write operations for virtio-blk
  • From: Chris Friesen <chris.friesen@xxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• Re: virtio DMA API?
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• virtio DMA API?
  • From: Andy Lutomirski <luto@xxxxxxxxxxxxxx>
• [WorldCIST'15]: Call for Workshops Proposals; Proceedings by Springer - Indexed by ISI, Scopus, DBLP, etc.
  • From: "ML" <marialemos72@xxxxxxxxx>
• RE: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <RAZYA@xxxxxxxxxx>
• Re: [V9fs-developer] [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [V9fs-developer] [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• Re: [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
  • From: Richard Yao <ryao@xxxxxxxxxx>
• Re: [Qemu-devel] QEMU dies on any attempt to load a Linux kernel module when using a 9P rootfs
  • From: Christopher Covington <cov@xxxxxxxxxxxxxx>
• RE: [PATCH] vhost: Add polling mode
  • From: David Laight <David.Laight@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <RAZYA@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <RAZYA@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Christian Borntraeger <borntraeger@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• RE: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• Re: [RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• RE: [RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• RE: [RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• RE: [RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• RE: [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• RE: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: "Bharat.Bhushan@xxxxxxxxxxxxx" <Bharat.Bhushan@xxxxxxxxxxxxx>
• Re: [PATCH 2/2] Install udev rules in system-default directory
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 2/2] Install udev rules in system-default directory
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <RAZYA@xxxxxxxxxx>
• Re: [PATCH net-next] vhost_net: stop rx net polling when possible
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <RAZYA@xxxxxxxxxx>
• Re: [PATCH net-next] vhost_net: stop rx net polling when possible
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH v3 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PULL] virtio-rng: add derating factor for use by hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH net-next] vhost_net: stop rx net polling when possible
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH v2 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: Razya Ladelsky <razya@xxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [3.16 stable PATCH 1/2] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [3.16 stable PATCH v2 2/2] Revert "hwrng: virtio - ensure reads happen after successful probe"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [3.16 stable PATCH v2 1/2] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [3.16 stable PATCH 1/2] virtio: rng: delay hwrng_register() till driver is ready
  • From: Greg KH <greg@xxxxxxxxx>
• [3.16 stable PATCH 2/2] Revert "hwrng: virtio - ensure reads happen after successful probe"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [3.16 stable PATCH 1/2] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [3.16 stable PATCH 1/1] virtio-rng: fix multi-device startup
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [3.16 stable PATCH 1/1] virtio-rng: fix multi-device startup
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [3.16 stable PATCH 1/1] virtio-rng: fix multi-device startup
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [3.16 stable PATCH 1/1] virtio-rng: fix multi-device startup
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH 1/1] virtio: rng: add derating factor for use by hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: Torsten Duwe <duwe@xxxxxx>
• [PATCH] vhost: Add polling mode
  • From: "Razya Ladelsky" <razya@xxxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>
• [3.16 stable PATCH 1/1] virtio-rng: fix multi-device startup
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PULL] virtio-next
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH] vhost: Add polling mode
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [WorldCIST'15]: Call for Workshops Proposals - Proceedings by Springer
  • From: "ML" <marialemos72@xxxxxxxxx>
• Re: [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: "H. Peter Anvin" <hpa@xxxxxxxxxxxxxxx>
• [PATCH 2/2] Install udev rules in system-default directory
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 1/2] rngd: add udev rule to source from hwrng if virtio-rng present
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 0/2] rng-tools: add udev rule for virtio-rng
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH] virtio-rng: complete have_data completion in removing device
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH] virtio-rng: complete have_data completion in removing device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
  • From: Stuart Yoder <b08248@xxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amos Kong <akong@xxxxxxxxxx>
• [PATCH] virtio-rng: complete have_data completion in removing device
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• RE: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: "arnab.basu@xxxxxxxxxxxxx" <arnab.basu@xxxxxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Jiang Liu <jiang.liu@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Arnd Bergmann <arnd@xxxxxxxx>
• Re: [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions
  • From: Eduardo Habkost <ehabkost@xxxxxxxxxx>
• Re: [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• [PATCH] x86, paravirt: BUG_ON on {rd,wr}msr exceptions
  • From: Eduardo Habkost <ehabkost@xxxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amos Kong <akong@xxxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: When I boot two virtio-rng devices, guest will hang
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [RFC PATCH 09/11] PCI/MSI: refactor PCI MSI driver
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 10/11] PCI/MSI: Split the generic MSI code into new file
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 11/11] x86/MSI: Refactor x86 MSI code
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 08/11] PCI/MSI: Introduce new struct msi_irqs and struct msi_ops
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 07/11] PCI/MSI: Mask MSI-X entry in msix_setup_entries()
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 03/11] PCI/MSI: Refactor pci_dev_msi_enabled()
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 02/11] PCI/MSI: Use new MSI type macro instead of PCI MSI flags
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 04/11] PCI/MSI: Move MSIX table address mapping out of msix_capability_init
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 05/11] PCI/MSI: Move populate_msi_sysfs() out of msi_capability_init()
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 06/11] PCI/MSI: Save MSI irq in PCI MSI layer
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 00/11] Refactor MSI to support Non-PCI device
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• [RFC PATCH 01/11] PCI/MSI: Use pci_dev->msi_cap instead of msi_desc->msi_attrib.pos
  • From: Yijing Wang <wangyijing@xxxxxxxxxx>
• Re: KVM Forum 2014 Call for Participation (reminder)
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v3 net-next 0/2] rx busy polling support for virtio-net
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PATCH v3 net-next 2/2] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH v3 net-next 1/2] virtio-net: introduce virtnet_receive()
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH v3 net-next 0/2] rx busy polling support for virtio-net
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Benoit Taine <benoit.taine@xxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio-rng: contribute to early randomness requests
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 0/4] virtio-rng: contribute to early randomness requests
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Bjorn Helgaas <bhelgaas@xxxxxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [PATCH v2 4/4] Revert "hwrng: virtio - ensure reads happen after successful probe"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 3/4] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 2/4] virtio: rng: re-arrange struct elements for better packing
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 0/4] virtio-rng: contribute to early randomness requests
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 1/4] virtio: rng: remove unused struct element
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 2/3] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 0/3] virtio-rng: contribute to early randomness requests
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 2/3] virtio: rng: delay hwrng_register() till driver is ready
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 3/3] Revert "hwrng: virtio - ensure reads happen after successful probe"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 1/3] virtio: rng: remove unused struct element
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH 23/25] virtio: Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Joe Perches <joe@xxxxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Dave Airlie <airlied@xxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Greg KH <greg@xxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: "Keller, Jacob E" <jacob.e.keller@xxxxxxxxx>
• Re: [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: "John W. Linville" <linville@xxxxxxxxxxxxx>
• [PATCH 23/25] virtio: Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Benoit Taine <benoit.taine@xxxxxxx>
• [PATCH 0/25] Replace DEFINE_PCI_DEVICE_TABLE macro use
  • From: Benoit Taine <benoit.taine@xxxxxxx>
• Re: [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH net-next V2 0/3] rx busy polling support for virtio-net
  • From: David Miller <davem@xxxxxxxxxxxxx>
• Re: [PATCH net-next] virtio-net: rx busy polling support
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH 3.13 077/198] block: virtio_blk: don't hold spin lock during world switch
  • From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
• [3.13.y.z extended stable] Patch "block: virtio_blk: don't hold spin lock during world switch" has been added to staging queue
  • From: Kamal Mostafa <kamal@xxxxxxxxxxxxx>
• Re: [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• [PATCH net-next V2 3/3] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH net-next V2 2/3] virtio-net: introduce virtnet_receive()
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH net-next V2 1/3] virtio-net: introduce helpers to enable and disable all NAPIs
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• [PATCH net-next V2 0/3] rx busy polling support for virtio-net
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH net-next] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Call for Papers: IEEE Transactions on Cloud Computing - Special Issue on Scientific Cloud Computing (deadline Jul 31, 2014)
  • From: Ioan Raicu <iraicu@xxxxxxxxxx>
• Re: [PATCH net-next] virtio-net: rx busy polling support
  • From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
• [PATCH net-next] virtio-net: rx busy polling support
  • From: Jason Wang <jasowang@xxxxxxxxxx>
• Re: [PATCH v3 0/2] hwrng, virtio-rng: init-time fixes
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v3 0/2] hwrng, virtio-rng: init-time fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/2] hwrng, virtio-rng: init-time fixes
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init"
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v3 0/2] hwrng, virtio-rng: init-time fixes
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [RFC PATCH 3/3] Revert "virtio: rng: ensure reads happen after successful probe"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [RFC PATCH 2/3] virtio: rng: only accept delayed early randomness requests
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [RFC PATCH 1/3] hw_random: allow RNG devices to give early randomness after a delay
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [RFC PATCH 0/3] hw_random: support for delayed init randomness requests
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init"
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init"
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• CFP: 7th IEEE Workshop on Many-Task Computing on Clouds, Grids, and Supercomputers (MTAGS) 2014 @ IEEE/ACM SC14
  • From: Ioan Raicu <iraicu@xxxxxxxxxx>
• Re: [PATCH v3 1/2] hwrng: fetch randomness only after device init
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [PATCH v3 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v3 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v3 0/2] hwrng, virtio-rng: init-time fixes
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Herbert Xu <herbert@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [RFC PATCH] hwrng: sysfs entry rng_seed_kernel, was: "Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init"
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [RFC V2 4/7] VSOCK: Introduce virtio-vsock.ko
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: [RFC V2 3/7] VSOCK: Introduce virtio-vsock-common.ko
  • From: Varka Bhadram <varkabhadram@xxxxxxxxx>
• Re: [PATCH 1/1] virtio: console: remove unnecessary null test before debugfs_remove_recursive
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH RFC 1/2] virtio: support for urgent descriptors
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 11/11] qspinlock, kvm: Add paravirt support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 07/11] qspinlock: Use a simple write to grab the lock, if applicable
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• VIRTIO/VHOST maintainer availability for 3.16/3.17
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH v2 2/2] virtio: rng: ensure reads happen after successful probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 1/2] hwrng: fetch randomness only after device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH v2 0/2] hwrng, virtio-rng: init-time fixes
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [RFC V2 7/7] Disable debug
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 6/7] VSOCK: Add Makefile and Kconfig
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 5/7] VSOCK: Introduce vhost-vsock.ko
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 4/7] VSOCK: Introduce virtio-vsock.ko
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 3/7] VSOCK: Introduce virtio-vsock-common.ko
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 2/7] VSOCK: Add dgram_skb to vsock_sock
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 1/7] VSOCK: Introduce vsock_find_unbound_socket and vsock_bind_dgram_generic
  • From: Asias He <asias.hejun@xxxxxxxxx>
• [RFC V2 0/7] Introduce VM Sockets virtio transport
  • From: Asias He <asias.hejun@xxxxxxxxx>
• Re: [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [PATCH 2/2 v2] hwrng: virtio: disable reading during probe
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] hwrng: don't fetch rng from sources without init
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• Re: [PATCH 1/2] hwrng: don't fetch rng from sources without init
  • From: Jason Cooper <jason@xxxxxxxxxxxxxx>
• [PATCH 1/1] ia64: use ARRAY_SIZE instead of sizeof/sizeof[0]
  • From: Fabian Frederick <fabf@xxxxxxxxx>
• [PATCH 1/1] virtio: console: remove unnecessary null test before debugfs_remove_recursive
  • From: Fabian Frederick <fabf@xxxxxxxxx>
• virt_blk BUG: sleeping function called from invalid context
  • From: Josh Boyer <jwboyer@xxxxxxxxxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: David Marchand <david.marchand@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: David Marchand <david.marchand@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: David Marchand <david.marchand@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: David Marchand <david.marchand@xxxxxxxxx>
• Re: [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Re: [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Kees Cook <keescook@xxxxxxxxxxxx>
• Re: [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [PATCH 1/2 v2] hwrng: Allow drivers to disable reading during probe
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH 1/2] hwrng: don't fetch rng from sources without init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 2/2] virtio: rng: introduce an init fn for hwrng core
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 1/2] hwrng: don't fetch rng from sources without init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• [PATCH 0/2] hwrng: don't fetch data before device init
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH driver-core-linus] kernfs: kernfs_notify() must be useable from non-sleepable contexts
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [RFC PATCH v2] Implement Batched (group) ticket lock
  • From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
• [PATCH RFC 2/2] vhost: support urgent descriptors
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH RFC 1/2] virtio: support for urgent descriptors
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [RFC PATCH v2] Implement Batched (group) ticket lock
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [RFC PATCH v2] Implement Batched (group) ticket lock
  • From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
• Re: [RFC PATCH v2] Implement Batched (group) ticket lock
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: virt_blk BUG: sleeping function called from invalid context
  • From: Tejun Heo <tj@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
• Re: [PATCH 1/1] virtio: console: remove unnecessary null test before debugfs_remove_recursive
  • From: Amit Shah <amit.shah@xxxxxxxxxx>
• Re: virt_blk BUG: sleeping function called from invalid context
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: virt_blk BUG: sleeping function called from invalid context
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: virt_blk BUG: sleeping function called from invalid context
  • From: Christoph Hellwig <hch@xxxxxx>
• Re: [PATCH v3 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v3 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: virt_blk BUG: sleeping function called from invalid context
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH 3.15 002/139] block: virtio_blk: dont hold spin lock during world switch
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• Virtualized desktop
  • From: Jimmy Thrasibule <thrasibule.jimmy@xxxxxxxxx>
• [RFC PATCH v2] Implement Batched (group) ticket lock
  • From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Cam Macdonell <cam@xxxxxxxxxxxxxx>
• Re: [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v3 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v3 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v3 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH v2 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v2 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [PATCH v2 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v2 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v2 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PULL] vhost: cleanups and fixes
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v1 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Dave Chinner <david@xxxxxxxxxxxxx>
• Re: [PATCH 11/11] qspinlock, kvm: Add paravirt support
  • From: Raghavendra K T <raghavendra.kt@xxxxxxxxxxxxxxxxxx>
• Re: [PATCH v1 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• [PATCH v1 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v1 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH v1 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 08/11] qspinlock: Revert to test-and-set on hypervisors
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 07/11] qspinlock: Use a simple write to grab the lock, if applicable
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 09/11] pvqspinlock, x86: Rename paravirt_ticketlocks_enabled
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Andreas Färber <afaerber@xxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 06/11] qspinlock: Optimize pending bit
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH v11 14/16] pvqspinlock: Add qspinlock para-virtualization support
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH 03/11] qspinlock: Add pending bit
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: Divide error in kvm_unlock_kick()
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Stefan Hajnoczi <stefanha@xxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [RFC PATCH 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH 10/11] qspinlock: Paravirt support
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH 08/11] qspinlock: Revert to test-and-set on hypervisors
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH 00/11] qspinlock with paravirt support
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Konrad Rzeszutek Wilk <konrad.wilk@xxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Jan Kiszka <jan.kiszka@xxxxxx>
• KVM Forum 2014 Call for Participation
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PATCH v11 14/16] pvqspinlock: Add qspinlock para-virtualization support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• [PATCH 11/11] qspinlock, kvm: Add paravirt support
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 10/11] qspinlock: Paravirt support
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 02/11] qspinlock, x86: Enable x86-64 to use queue spinlock
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 08/11] qspinlock: Revert to test-and-set on hypervisors
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 09/11] pvqspinlock, x86: Rename paravirt_ticketlocks_enabled
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 06/11] qspinlock: Optimize pending bit
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 03/11] qspinlock: Add pending bit
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 05/11] qspinlock: Optimize for smaller NR_CPUS
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 01/11] qspinlock: A simple generic 4-byte queue spinlock
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 07/11] qspinlock: Use a simple write to grab the lock, if applicable
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 04/11] qspinlock: Extract out the exchange of tail code word
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• [PATCH 00/11] qspinlock with paravirt support
  • From: Peter Zijlstra <a.p.zijlstra@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Olivier MATZ <olivier.matz@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Jobin Raju George <jobin.rv@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Jobin Raju George <jobin.rv@xxxxxxxxx>
• Re: [RFC PATCH 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Jens Axboe <axboe@xxxxxxxxx>
• [RFC PATCH 2/2] block: virtio-blk: support multi virt queues per virtio-blk device
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [RFC PATCH 1/2] include/uapi/linux/virtio_blk.h: introduce feature of VIRTIO_BLK_F_MQ
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [RFC PATCH 0/2] block: virtio-blk: support multi vq per virtio-blk
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• Re: [PATCH v1] vhost: avoid large order allocations
  • From: Michael Mueller <mimu@xxxxxxxxxxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• Re: [Qemu-devel] Why I advise against using ivshmem
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: Why is virtio_console not a tty?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: Why is virtio_console not a tty?
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: Waiman Long <waiman.long@xxxxxx>
• Re: [PATCH v11 14/16] pvqspinlock: Add qspinlock para-virtualization support
  • From: Waiman Long <waiman.long@xxxxxx>
• Why is virtio_console not a tty?
  • From: "H. Peter Anvin" <hpa@xxxxxxxxx>
• Re: [PATCH] vhost-scsi: don't open-code kvfree
  • From: "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx>
• Re: [PATCH] vhost-scsi: don't open-code kvfree
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Why I advise against using ivshmem
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: Why I advise against using ivshmem
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• [PATCH] vhost-scsi: don't open-code kvfree
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Why I advise against using ivshmem (was: [Qemu-devel] Using virtio for inter-VM communication)
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
• Re: [Qemu-devel] Using virtio for inter-VM communication
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
• Re: [PULL] vhost: infrastructure changes for 3.16
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• Re: [PULL] vhost: infrastructure changes for 3.16
  • From: Romain Francoise <romain@xxxxxxxxxxxxx>
• Re: [PATCH v11 14/16] pvqspinlock: Add qspinlock para-virtualization support
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Henning Schild <henning.schild@xxxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Markus Armbruster <armbru@xxxxxxxxxx>
• Re: [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Jan Kiszka <jan.kiszka@xxxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: "Long, Wai Man" <waiman.long@xxxxxx>
• Re: [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: "Long, Wai Man" <waiman.long@xxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• [PULL] vhost: infrastructure changes for 3.16
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: Peter Zijlstra <peterz@xxxxxxxxxxxxx>
• Re: Using virtio for inter-VM communication
  • From: Vincent JARDIN <vincent.jardin@xxxxxxxxx>
• Using virtio for inter-VM communication
  • From: Henning Schild <henning.schild@xxxxxxxxxxx>
• [PATCH 3.4 45/88] virtio-blk: Call del_gendisk() before disable guest kick
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• [PATCH 3.4 46/88] virtio-blk: Reset device after blk_cleanup_queue()
  • From: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
• ICAC14 Call For Participation
  • From: Ming Zhao <zhaom@xxxxxxxxxxx>
• [PATCH v2 2/2] vhost: move memory pointer to VQs
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH v2 1/2] vhost: move acked_features to VQs
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH 1/2] vhost: move acked_features to VQs
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH 2/2] vhost: move memory pointer to VQs
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PATCH 1/2] vhost: move acked_features to VQs
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Vlad Yasevich <vyasevich@xxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• Re: [PULL 2/2] vhost: replace rcu with mutex
  • From: Eric Dumazet <eric.dumazet@xxxxxxxxx>
• Re: [PULL net-next] vhost enhancements for 3.16
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PULL 2/2] vhost: replace rcu with mutex
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PULL 1/2] vhost-net: extend device allocation to vmalloc
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• [PULL 0/2] vhost enhancements for 3.16
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PULL net-next] vhost enhancements for 3.16
  • From: David Miller <davem@xxxxxxxxxxxxx>
• [PULL net-next] vhost enhancements for 3.16
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Jens Axboe <axboe@xxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Rusty Russell <rusty@xxxxxxxxxxxxxxx>
• Re: Divide error in kvm_unlock_kick()
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: question about "struct kvm_segment"
  • From: Jidong Xiao <jidong.xiao@xxxxxxxxx>
• Re: question about "struct kvm_segment"
  • From: Paolo Bonzini <pbonzini@xxxxxxxxxx>
• [PATCH v11 16/16] pvqspinlock, x86: Enable PV qspinlock for XEN
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 15/16] pvqspinlock, x86: Enable PV qspinlock PV for KVM
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 14/16] pvqspinlock: Add qspinlock para-virtualization support
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 13/16] pvqspinlock: Enable coexistence with the unfair lock
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 12/16] pvqspinlock, x86: Add PV data structure & methods
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 11/16] pvqspinlock, x86: Rename paravirt_ticketlocks_enabled
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 10/16] qspinlock: Split the MCS queuing code into a separate slowerpath
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 09/16] qspinlock, x86: Allow unfair spinlock in a virtual guest
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 08/16] qspinlock: Prepare for unfair lock support
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 07/16] qspinlock: Use a simple write to grab the lock, if applicable
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 06/16] qspinlock: prolong the stay in the pending bit path
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 05/16] qspinlock: Optimize for smaller NR_CPUS
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 04/16] qspinlock: Extract out the exchange of tail code word
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 03/16] qspinlock: Add pending bit
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 02/16] qspinlock, x86: Enable x86-64 to use queue spinlock
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 01/16] qspinlock: A simple generic 4-byte queue spinlock
  • From: Waiman Long <Waiman.Long@xxxxxx>
• [PATCH v11 00/16] qspinlock: a 4-byte queue spinlock with PV support
  • From: Waiman Long <Waiman.Long@xxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Ming Lei <ming.lei@xxxxxxxxxxxxx>
• Re: Divide error in kvm_unlock_kick()
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: Divide error in kvm_unlock_kick()
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Divide error in kvm_unlock_kick()
  • From: Chris Webb <chris@xxxxxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: "Michael S. Tsirkin" <mst@xxxxxxxxxx>
• Re: [PATCH] block: virtio_blk: don't hold spin lock during world switch
  • From: Jens Axboe <axboe@xxxxxxxxx>