30 May, 2011

1 commit

  • It's unclear to me if it's important, but it's obviously causing my
    technical colleages some headaches and I'd hate such imprecision to
    slow virtio adoption.

    I've emailed this to all non-trivial contributors for approval, too.

    Signed-off-by: Rusty Russell
    Acked-by: Grant Likely
    Acked-by: Ryan Harper
    Acked-by: Anthony Liguori
    Acked-by: Eric Van Hensbergen
    Acked-by: john cooper
    Acked-by: Aneesh Kumar K.V
    Acked-by: Christian Borntraeger
    Acked-by: Fernando Luis Vazquez Cao

    Rusty Russell
     

12 Jun, 2009

1 commit

  • This implements optional MSI-X support in virtio_pci.
    MSI-X is used whenever the host supports at least 2 MSI-X
    vectors: 1 for configuration changes and 1 for virtqueues.
    Per-virtqueue vectors are allocated if enough vectors
    available.

    Signed-off-by: Michael S. Tsirkin
    Acked-by: Anthony Liguori
    Signed-off-by: Rusty Russell (+ whitespace, style)

    Michael S. Tsirkin
     

30 Dec, 2008

2 commits


25 Jul, 2008

1 commit


04 Feb, 2008

2 commits

  • As Avi pointed out, as we continue to massage the virtio PCI ABI, we can make
    things a little more friendly to users by utilizing the PCI revision field to
    indicate which version of the ABI we're using. This is a hard ABI version
    and incrementing it will cause the guest driver to break.

    This is the necessary changes to virtio_pci to support this.

    Signed-off-by: Anthony Liguori
    Signed-off-by: Rusty Russell

    Anthony Liguori
     
  • This is a PCI device that implements a transport for virtio. It allows virtio
    devices to be used by QEMU based VMMs like KVM or Xen.

    Signed-off-by: Anthony Liguori
    Signed-off-by: Rusty Russell

    Anthony Liguori